Runway Incursion Prevention: A Flight School SOP for Hot Spots, Hold-Short, and Taxi Briefings

A student calls for taxi at a Class D field with two runways, gets "taxi to runway 27 via Alpha, cross runway 22," reads back "taxi 27 via Alpha," and starts rolling. The instructor catches the missed cross-runway instruction before the run-up, has the student read it back correctly, and lets the taxi continue. The lesson goes on. The incident never made a report. The next time that student flies with a different instructor who is heads-down looking for the checklist, the same missed readback rolls past the hold-short line before anyone catches it. That is a runway incursion, and it is how almost every one of them starts.

The FAA classifies a runway incursion as any occurrence at an aerodrome involving the incorrect presence of an aircraft, vehicle, or person on the protected area of a surface designated for the landing and takeoff of aircraft. The FAA Runway Safety Program tracks them and publishes annual counts by airport and by category. Category A and B events are the ones with actual collision potential. Category C and D are the ones where the pilot deviation happened but the geometry did not put anyone in immediate danger. Flight training operations show up disproportionately in the pilot-deviation column, and they show up at the same handful of complex airports year after year.

The Surface Is a Training Environment

The airport surface gets treated as the walk to the airplane. It is not. Taxiing is a phase of flight the airplane spends more time in during a primary syllabus than any other phase except cruise, and it is the phase where the highest-severity events happen at the lowest airspeeds. A school that treats taxi as an administrative segment between pushback and takeoff is teaching students to relax exactly where the surface data says they should be tightening up.

The correction is small and specific. Every flight, before the engine starts, the student pulls out the airport diagram and briefs the expected taxi routing aloud. Where is the run-up. Which taxiway gets there. What runways are crossed on the way. Where are the hot spots on today's diagram. That briefing takes ninety seconds. It moves the taxi from a reactive stream of controller instructions into a plan the student is comparing the clearance against.

Hot Spots Are Not Trivia

FAA charts mark hot spots at the airports where the surface geometry has produced repeated incidents. A hot spot is not a warning to be alert generically. It is a specific piece of pavement where a converging taxiway, a non-standard hold-short line, or a confusing intersection has caught pilots more than once. Every home-field syllabus should teach the local hot spots by number. A student who cannot point to HS-1 on their own airport diagram and say what makes it a hot spot has not been trained on the field they are flying out of.

This is the piece that carries over to unfamiliar airports on cross-countries. A student who has been drilled on the home field's hot spots knows to look for them on any diagram, and their pre-taxi briefing at a strange field is not the first time they have ever practiced the habit. The AC 91-73B advisory on aircraft ground operations is the reference the FAA leans on for surface procedures, and its guidance is the same one the school SOP should mirror.

Hold-Short Readbacks Are Not Optional

The most common runway incursion category at flight training airports is a missed hold-short readback. A controller who issues a hold-short instruction is required to receive it back verbatim. A pilot who does not read it back has not been given the clearance the controller thinks they gave. This is exactly the readback discipline covered in towered airport operations, and it is where the surface event that becomes a Category A incursion almost always begins.

A school SOP can enforce this without inventing anything new. Any taxi instruction that contains "hold short" gets read back with the runway number, the taxiway, and the aircraft callsign. The student says it. The instructor confirms it. If the student misses the hold-short element, the instructor does not paraphrase it back to the controller. The student re-reads it. The habit that survives the checkride is the habit that was corrected at the source, not the one that was covered by a smoother instructor voice.

The Non-Towered Version of the Same Problem

Runway incursions happen at non-towered fields too, and the mechanism is different. There is no controller to issue a hold-short. The pilot is responsible for verifying the runway is clear before crossing and before entering to take off. The self-announce discipline covered in non-towered airport operations is what backfills that responsibility. A student who lines up on the runway without a positive verbal check that final is clear, in visual meaning as well as radio, is a student who will eventually do it at a field where an inbound aircraft was silent on the wrong frequency.

The SOP for a non-towered field should require the same verbal callout every takeoff. "Final clear, runway clear, taking runway 27." The instructor says it. The student says it. Every time. The muscle memory of that callout is what a solo student falls back on when the pattern is unfamiliar and the workload is up.

Stage Checks Catch What the Line Does Not

The instructor who flies with a student every lesson stops seeing the drift. The taxi briefing gets skipped once because the flight is tight, then twice because the student already knows the field. A stage check with a different instructor is where that drift surfaces. Surface procedures are one of the items the stage check instructor should evaluate deliberately, not roll into the general operations grade. Did the student brief the taxi. Did they read back the hold-short verbatim. Did they identify the hot spots on the diagram before rolling. If not, that is a Stage One re-do on the ground procedures, not a mark on a form.

The same rigor belongs in the CFI standardization meeting. A school where one instructor drills the hold-short readback and another lets the student mumble it is a school with two different surface programs. Standardization is the mechanism by which the SOP a chief instructor wrote actually becomes the SOP a student experiences. Without it, the document on the wall and the behavior on the ramp diverge in ways that only show up when the NASA report gets filed.

Making It Part of Dispatch

The dispatch desk sees the surface as a schedule input, not a safety one. It does not have to be that way. A school whose fleet is dispatched through a platform can tag which students have completed a hot spot briefing for the home field, which have flown into the local Class C with its own set of hot spots, and which are still on the pre-solo checklist for surface procedures. When the dispatcher can see those tags at booking time, a first-time cross-country to an airport with three published hot spots does not go out without the instructor having briefed them.

The point is not to add friction. It is to make the surface program a scheduling input the same way a solo endorsement already is. A student is either signed off for the field they are flying to, or the booking flags. That is the version of runway incursion prevention that actually holds under Saturday-morning volume, when the chief instructor is not walking every airplane to the run-up.

The Habit That Ends the Category

Runway incursions do not usually get solved by a poster in the pilot lounge. They get solved by a school that treats the taxi as a phase of flight, briefs it, reads back every hold-short verbatim, tracks hot spots on the diagram, and evaluates all of it in stage checks. The airports that show up on the annual runway safety report year after year are not the ones with the worst pavement geometry. They are the ones where the training operations at that field never made the surface part of the syllabus. The schools that quietly stopped appearing on that list are the ones that decided the ninety-second pre-taxi briefing was cheaper than the phone call that comes after a Category A event.