Lost Procedures

Five skill elements, none of them with a numeric tolerance (CA.VI.D.S1–S5):

• Use an appropriate method to determine position
• Maintain an appropriate heading and climb as necessary
• Identify prominent landmarks
• Use navigation systems or facilities or contact an ATC facility for assistance
• Select an appropriate course of action

The objective language is worth reading closely — you must "take appropriate steps to achieve a satisfactory outcome if lost." This is a decision-making task graded on process, not on a needle.

PHAK 16-34 gives the sequence in plain terms:

1. Climb — if a town or city cannot be seen, "the first thing to do is climb, being mindful of traffic and weather conditions." An increase in altitude "increases radio and navigation reception range and also increases radar coverage."
2. Look — if flying near a town or city, "it may be possible to read the name of the town on a water tower."
3. Fix your position — with a VOR or ADF receiver, "determine position by plotting an azimuth from two or more navigational facilities." If GPS or a portable aviation GPS is on board, use it for position and the nearest airport.
4. Communicate — "using frequencies shown on the sectional chart." A controller may offer radar vectors; other facilities may offer direction finding (DF) assistance.
5. Escalate — transmit on 121.5 MHz and squawk 7700; PHAK notes most facilities and even airliners monitor the emergency frequency.

PHAK's framing is worth quoting on the oral: getting lost "is a potentially dangerous situation, especially when low on fuel." Fuel is the clock on the whole problem.

The controller "requests the pilot to hold down the transmit button for a few seconds and then release it." You may be asked to change directions a few times and repeat the transmit procedure, which gives the controller enough information to establish your position and steer you.

Two practical notes: your transmissions must be on a frequency the DF facility can receive, and DF is worth remembering because it works when your navigation receivers do not — it is the fallback with the fewest dependencies on your airplane's equipment.

Because wandering destroys the one asset you still have: a last known position plus a heading and a clock. Dead reckoning from a known fix is only valid if the heading and airspeed were steady — PHAK 16-13 defines dead reckoning as computation "based on time, airspeed, distance, and direction," and a random-direction search invalidates all four.

So: hold a heading, hold an altitude, and let the DR circle stay small enough to be useful. The circling advice you learned for the private ride is for staying over a recognizable feature while you work — not for burning fuel in a hold.

Size and uniqueness. PHAK 16-18's checkpoint guidance applies with more force when you are already unsure: use large towns, large lakes and rivers, or combinations of recognizable points — a town with an airport, a town with a network of highways and railroads. Choose towns shown as splashes of yellow, not towns drawn as a small circle, which "may turn out to be only a half-dozen houses."

The failure mode is confirmation bias: finding a small feature that could be the one you want and then bending the rest of the picture to fit it. A single ambiguous match is not a fix. Confirm with a second, independent feature — a river bend plus a highway crossing plus a bearing from a VOR.

• Two VOR radials: tune and ident two stations, center each needle with a FROM indication, and plot both radials on the sectional. Their intersection is your position (PHAK 16-34, "plotting an azimuth from two or more navigational facilities").
• One radial plus a distance: a radial with DME gives a fix from a single station.
• GPS: direct position and nearest airport, subject to the RAIM and database cautions of Task VI.B — with no RAIM alerting, PHAK 16-32 says to be suspicious of a GPS position that disagrees with other navigation, pilotage, or dead reckoning.
• ATC radar: an ident on an assigned squawk and the controller can tell you where you are (PHAK 14-26).

Cross-check whichever one you use against your dead reckoning. Two agreeing sources is a fix; one is a hypothesis.

Because it converts "lost" into an arithmetic problem — with these three, you can compute distance flown and draw a small circle of uncertainty:

• Time: at your last positive fix
• Heading: flown since
• Groundspeed: already measured

Without those times you are searching the whole chart.

It is the same habit Task VI.A grades — a time in the box at every checkpoint. The examiner may well ask this question specifically to see whether you have been keeping the log honestly all flight, or filling it in from memory.

Early, and earlier than feels comfortable. The trigger points to name:

• Ask for help the moment you have an unresolved position and the situation is not improving — a request for radar assistance costs you nothing.
• Declare an emergency when fuel, daylight, or weather is deteriorating toward a forced outcome. The PIC has authority to deviate from any rule of part 91 to the extent required to meet an in-flight emergency (91.3(b)); a written report is required only upon the request of the Administrator (91.3(c)).
• 121.5 MHz and squawk 7700 if you cannot raise anyone on a published frequency (PHAK 16-34).

The professional framing: the cost of asking early is a phone number; the cost of asking late is the accident report. Fuel exhaustion while sorting out a navigation problem is a decision, not an event.

Pick the outcome that ends the problem with margin, not the one that saves face:

• Reintercept the planned route if the fix is solid, the fuel is comfortable, and the weather ahead is what you briefed.
• Divert to the nearest suitable airport if fuel, daylight, or weather has eroded — that is Task VI.C, and the estimate work is identical.
• Land and sort it out on the ground. An unplanned landing at a suitable airport with fuel in the tanks is a non-event; the same landing with the tanks dry is an accident.

State the decision out loud with the reason and the number that drove it. That is what separates a commercial answer from a private one.

• A time at every checkpoint — the ACS asks only that times be recorded over waypoints (CA.VI.D.R3) and that you make en route checkpoints within three minutes of the initial or revised ETA (CA.VI.A.S6). Spacing checkpoints so no fix is ever more than about fifteen minutes old is technique, not a standard, but it keeps the DR circle small.
• Position verified within 2 NM of the planned route continuously, not reconstructed later (CA.VI.A.S5).
• Two independent sources agreeing — pilotage against the sectional and an electronic position. PHAK 16-32: "VFR pilots should never rely solely on one system of navigation."
• Flight following, so a controller is watching your target and will tell you when your track stops making sense (PHAK 14-26).
• A current database and a current chart. PHAK 16-32 records that "numerous pilots have ventured into airspace they were trying to avoid by using an outdated database."
• Say the doubt early. The gap between "something looks off" and "I am lost" is usually ten minutes of silence.

Disorientation is almost always downstream of something else — a passenger conversation, a systems annunciation, a reprogramming task, or a weather deviation that pulled you off the planned track without your updating the plan.

The commercial-level mitigation is to treat any deviation as a new leg: new heading, new time, new estimate, spoken aloud. A deviation you never wrote down becomes an unknown position an hour later. Similarly, PHAK 16-33's advice to minimize head-down time and keep a sharp lookout applies directly — the same head-down minutes that create the traffic hazard are the ones in which the ground picture gets away from you.

Three that are worth naming:

• The climb. PHAK 16-34's first step is to climb, "being mindful of traffic and weather conditions" — you are ascending through altitudes you have not been scanning, possibly into a hemispheric cruising altitude flown by aircraft you cannot see, and possibly toward cloud you must remain clear of.
• Circling and maneuvering over a landmark puts you in a nonstandard flight path near a town that may have an airport under it, and your track no longer matches the clock position of any traffic call.
• Head-down time while plotting radials or working the GPS — the single largest see-and-avoid degrader in this task.

Mitigations: level off and trim before you compute, get radar traffic advisories, keep the landing light on, and put the airplane on a steady heading so ATC and other traffic can predict you.