Narrative:

Student was on inbound leg of cross country solo, destination bdr (sikorsky, bridgeport, ct). Despite monitoring visual chkpoints, inadvertently deviated from course and approached tweed-new haven (hvn). Contributing factors: both hvn and bdr are on long island sound, similarly situated south of moderately sized cities and south of a major highway (I-95). Both airports have 2 crossing runways (differently configured, of course). Student pilot recognized runway confign as different from bdr. On this realization, the pilot instantly recognized various landmarks around new haven, with which he was familiar. No conflict was present and no evasive action was necessary at any time. The student pilot left the pattern at hvn, taking care as always to fulfill the VFR obligation to 'see and avoid' other aircraft. Pilot reported the error to bdr tower (in continuous radio contact). Then, pilot contacted hvn tower to report the error and apologize. Hvn tower mentioned that there were other aircraft in the pattern. Pilot acknowledged this and again apologized. Pilot then proceeded west to bdr. Bdr tower was then contacted, remainder of trip, including landing at bdr and home to westchester county/hpn was uneventful. Conditions were as cavu as cavu gets. The student could clearly see the wrong city (new haven) and wrong airport (hvn) from at least 20 mi away, and became convinced they were bridgeport and bdr. The student pilot's mind began ignoring various pieces of evidence that were inconsistent with an approach to bdr. A contributing factor may have been a strong desire to complete a successful cross country trip. Despite the similarities of bdr and hvn, the following differences (decisive, of course) were disregarded: VOR tuned to bdr showed progressive deviation from course. Bdr tower reported no visual or radar identify of the aircraft after initial radio contact. Missing from hvn was a 'candy stripe' smokestack near the field and other features characteristic of bdr. The hvn runways are aligned differently from bdr. Although the student pilot eventually recognized this, his initial thought was that the magnetic compass might have been inaccurate on descent, and that the magnetic heading indicator may have precessed. If your intended tower doesn't have visual or radar contact, reconsider your position! Don't let perceptions about the flying environment (position) become so entrenched that evidence to the contrary is ignored. Be especially careful in discounting or explaining away information (visual, instrument, communications from ATC) inconsistent with perceived position.

Google
 

Original NASA ASRS Text

Title: C172 STUDENT PLT LINED UP ON HVN INSTEAD OF HIS INTENDED POINT OF LNDG BDR. THE PLT EXCUSED HIMSELF AFTER HE SAW THE ERROR, AND PROCEEDED TO BDR.

Narrative: STUDENT WAS ON INBOUND LEG OF XCOUNTRY SOLO, DEST BDR (SIKORSKY, BRIDGEPORT, CT). DESPITE MONITORING VISUAL CHKPOINTS, INADVERTENTLY DEVIATED FROM COURSE AND APCHED TWEED-NEW HAVEN (HVN). CONTRIBUTING FACTORS: BOTH HVN AND BDR ARE ON LONG ISLAND SOUND, SIMILARLY SITUATED S OF MODERATELY SIZED CITIES AND S OF A MAJOR HWY (I-95). BOTH ARPTS HAVE 2 XING RWYS (DIFFERENTLY CONFIGURED, OF COURSE). STUDENT PLT RECOGNIZED RWY CONFIGN AS DIFFERENT FROM BDR. ON THIS REALIZATION, THE PLT INSTANTLY RECOGNIZED VARIOUS LANDMARKS AROUND NEW HAVEN, WITH WHICH HE WAS FAMILIAR. NO CONFLICT WAS PRESENT AND NO EVASIVE ACTION WAS NECESSARY AT ANY TIME. THE STUDENT PLT LEFT THE PATTERN AT HVN, TAKING CARE AS ALWAYS TO FULFILL THE VFR OBLIGATION TO 'SEE AND AVOID' OTHER ACFT. PLT RPTED THE ERROR TO BDR TWR (IN CONTINUOUS RADIO CONTACT). THEN, PLT CONTACTED HVN TWR TO RPT THE ERROR AND APOLOGIZE. HVN TWR MENTIONED THAT THERE WERE OTHER ACFT IN THE PATTERN. PLT ACKNOWLEDGED THIS AND AGAIN APOLOGIZED. PLT THEN PROCEEDED W TO BDR. BDR TWR WAS THEN CONTACTED, REMAINDER OF TRIP, INCLUDING LNDG AT BDR AND HOME TO WESTCHESTER COUNTY/HPN WAS UNEVENTFUL. CONDITIONS WERE AS CAVU AS CAVU GETS. THE STUDENT COULD CLRLY SEE THE WRONG CITY (NEW HAVEN) AND WRONG ARPT (HVN) FROM AT LEAST 20 MI AWAY, AND BECAME CONVINCED THEY WERE BRIDGEPORT AND BDR. THE STUDENT PLT'S MIND BEGAN IGNORING VARIOUS PIECES OF EVIDENCE THAT WERE INCONSISTENT WITH AN APCH TO BDR. A CONTRIBUTING FACTOR MAY HAVE BEEN A STRONG DESIRE TO COMPLETE A SUCCESSFUL XCOUNTRY TRIP. DESPITE THE SIMILARITIES OF BDR AND HVN, THE FOLLOWING DIFFERENCES (DECISIVE, OF COURSE) WERE DISREGARDED: VOR TUNED TO BDR SHOWED PROGRESSIVE DEV FROM COURSE. BDR TWR RPTED NO VISUAL OR RADAR IDENT OF THE ACFT AFTER INITIAL RADIO CONTACT. MISSING FROM HVN WAS A 'CANDY STRIPE' SMOKESTACK NEAR THE FIELD AND OTHER FEATURES CHARACTERISTIC OF BDR. THE HVN RWYS ARE ALIGNED DIFFERENTLY FROM BDR. ALTHOUGH THE STUDENT PLT EVENTUALLY RECOGNIZED THIS, HIS INITIAL THOUGHT WAS THAT THE MAGNETIC COMPASS MIGHT HAVE BEEN INACCURATE ON DSCNT, AND THAT THE MAGNETIC HEADING INDICATOR MAY HAVE PRECESSED. IF YOUR INTENDED TWR DOESN'T HAVE VISUAL OR RADAR CONTACT, RECONSIDER YOUR POS! DON'T LET PERCEPTIONS ABOUT THE FLYING ENVIRONMENT (POS) BECOME SO ENTRENCHED THAT EVIDENCE TO THE CONTRARY IS IGNORED. BE ESPECIALLY CAREFUL IN DISCOUNTING OR EXPLAINING AWAY INFO (VISUAL, INST, COMS FROM ATC) INCONSISTENT WITH PERCEIVED POS.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.