Narrative:

The primary factor leading to the incident was that neither crew member had flown the route. There were numerous contributing factors leading to the outcome of the day. The captain attempted to place the IATA identify into the GPS and failed. He then tried the nearest navigation facility which was flp VOR and this was accepted by the GPS. Runway finals to both flp airport and bpk airport are parallel and long final to bpk runs right over the flp airport. From the beginning, the day was rushed and always behind schedule. It was simultaneously discovered when a non revenue passenger approached the flight crew and told them of the correct position of the destination airport. Flight crew departed flp and landed at bpk without incident or any unusual circumstances. Flight crew failed to contact operations before departing flp airport. Supplemental information from acn 421400: the crew landed at the wrong airport. Instead of terminating the flight and contacting flight operations, they chose to take off again and land at the proper destination airport, which was 5.5 NM away. After landing at the proper destination airport, they realized that they had departed without proper dispatch authority/authorized. In doing so, they violated several FARS. During the crew briefing, the captain stated that the GPS was set up to go to flp. I asked what flp was, and he replied that it was 'the VOR near the airport.' I did not consider his inability to get the GPS to recognize the destination airport as significant. I assumed that since the WX was good, that once we got close to the flp VOR we could get a visual approach to the airport. 5-7 mi away was the last time I recall referencing the GPS during the flight. We continued the day's scheduled flts without notifying operations.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLC LANDED AT WRONG ARPT AND THEN DEPARTED WITHOUT A DISPATCH RELEASE.

Narrative: THE PRIMARY FACTOR LEADING TO THE INCIDENT WAS THAT NEITHER CREW MEMBER HAD FLOWN THE RTE. THERE WERE NUMEROUS CONTRIBUTING FACTORS LEADING TO THE OUTCOME OF THE DAY. THE CAPT ATTEMPTED TO PLACE THE IATA IDENT INTO THE GPS AND FAILED. HE THEN TRIED THE NEAREST NAV FACILITY WHICH WAS FLP VOR AND THIS WAS ACCEPTED BY THE GPS. RWY FINALS TO BOTH FLP ARPT AND BPK ARPT ARE PARALLEL AND LONG FINAL TO BPK RUNS RIGHT OVER THE FLP ARPT. FROM THE BEGINNING, THE DAY WAS RUSHED AND ALWAYS BEHIND SCHEDULE. IT WAS SIMULTANEOUSLY DISCOVERED WHEN A NON REVENUE PAX APCHED THE FLC AND TOLD THEM OF THE CORRECT POS OF THE DEST ARPT. FLC DEPARTED FLP AND LANDED AT BPK WITHOUT INCIDENT OR ANY UNUSUAL CIRCUMSTANCES. FLC FAILED TO CONTACT OPS BEFORE DEPARTING FLP ARPT. SUPPLEMENTAL INFO FROM ACN 421400: THE CREW LANDED AT THE WRONG ARPT. INSTEAD OF TERMINATING THE FLT AND CONTACTING FLT OPS, THEY CHOSE TO TAKE OFF AGAIN AND LAND AT THE PROPER DEST ARPT, WHICH WAS 5.5 NM AWAY. AFTER LNDG AT THE PROPER DEST ARPT, THEY REALIZED THAT THEY HAD DEPARTED WITHOUT PROPER DISPATCH AUTH. IN DOING SO, THEY VIOLATED SEVERAL FARS. DURING THE CREW BRIEFING, THE CAPT STATED THAT THE GPS WAS SET UP TO GO TO FLP. I ASKED WHAT FLP WAS, AND HE REPLIED THAT IT WAS 'THE VOR NEAR THE ARPT.' I DID NOT CONSIDER HIS INABILITY TO GET THE GPS TO RECOGNIZE THE DEST ARPT AS SIGNIFICANT. I ASSUMED THAT SINCE THE WX WAS GOOD, THAT ONCE WE GOT CLOSE TO THE FLP VOR WE COULD GET A VISUAL APCH TO THE ARPT. 5-7 MI AWAY WAS THE LAST TIME I RECALL REFING THE GPS DURING THE FLT. WE CONTINUED THE DAY'S SCHEDULED FLTS WITHOUT NOTIFYING OPS.

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.