The background of this incident involves a pilot mistaking Cambridge Airport for Duxford Airfield.

1. Situation

The pilot was flying VFR in a biplane with limited avionics, intending to land at Duxford Airfield (EGSU).

Having never flown to Duxford before, the pilot sought tips from a friend familiar with the airfield.

The friend described Duxford as having a south-westerly hard runway with a parallel grass runway and a petrol station on the final approach path, with hangars and a tower to the north on the right-hand side during the approach.

2. Task

The task was to navigate to and land at Duxford Airfield safely, using the provided visual cues and following VFR procedures.

3. Action

The flight was uneventful, and the pilot contacted Duxford Information to announce a straight-in approach to runway 24.

The Duxford FISO confirmed and later instructed the pilot to land at their discretion.

On final approach, the pilot passed a petrol station, saw hangars on the right, and landed on the hard runway with a parallel grass runway, believing everything had gone as planned.

However, they had mistakenly landed at Cambridge Airport (EGSC), which shares similar characteristics with Duxford but is 8 miles away.

4. Result

Despite landing at the wrong airport without clearance, there were no harmful outcomes.

This incident underscores the importance of confirming locations to avoid confirmation bias.

Wrong airport landings have a long history, but modern avionics can help reduce their frequency. Nonetheless, even with GPS, pilots can misidentify airfields and convince themselves they are at the correct destination.

The lesson learnt is to thoroughly verify the intended location, utilise all available navigation aids, and remain cautious of confirmation bias to ensure accurate identification of the destination airfield.

Warning signs to notice earlier

• Visual cues are being used only to confirm the expected airfield rather than to test competing possibilities.
• Position, distance or radio information does not fit perfectly, but the mismatch is being explained away.
• A straight-in arrival removes circuit geometry that might otherwise expose the wrong location.

Decision analysis

Confirmation bias becomes powerful when several generic cues match: runway direction, nearby buildings and a familiar-looking landmark. The defence is an active disconfirmation step. Ask what would prove this is the wrong aerodrome, then compare independent identifiers such as charted position, distance and bearing, runway layout, radio calls, navigation display and distinctive features.

Radio contact alone is not proof of position. A unit may hear a call while the aircraft is elsewhere, and an expected response can be interpreted too generously. Report an accurate position and challenge any inconsistency before joining or landing.

Safer alternatives to discuss

Brief a positive identification gate before descent. If the aerodrome cannot be identified from multiple independent cues by that gate, remain clear, reposition or request assistance rather than continuing an approach that merely looks plausible.

Instructor or group debrief

1. Which cues were distinctive and which were shared by both aerodromes?
2. What independent navigation check would have exposed the error earliest?
3. How did the straight-in plan reduce opportunities to cross-check?
4. What exact gate would stop the next approach?

Do not copy actions from this learning scenario into an aircraft checklist. Transfer the decision-making lesson, then use current official information, approved aircraft procedures and qualified instruction for the operation itself.

How to use this case responsibly

Separate the evidence from the teaching interpretation. First list only what the cited source or scenario actually establishes. Then list the assumptions that would need checking: aircraft variant, installed equipment, weather, runway state, pilot qualification, local procedures and the exact sequence of events. This prevents a memorable story from becoming an invented checklist.

Before the next relevant flight, turn one lesson into a concrete briefing item or decision gate and verify it against the current AFM or POH, official aeronautical information and operator procedures. If the case exposes a skill gap, rehearse it with a qualified instructor under suitable conditions. After the flight, record whether the warning sign appeared, whether the gate was usable and what should change next time.

For a group debrief, ask which decision was last easily reversible, which cue was available at that moment and what pressure encouraged continuation. Compare at least two safer alternatives and identify the new risks each would introduce. The aim is not hindsight blame; it is to build options early enough that the safest action remains practical.