37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 631475 |
Time | |
Date | 200409 |
Day | Sun |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : bec.airport |
State Reference | KS |
Altitude | agl bound lower : 0 agl bound upper : 1000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : ict.tracon |
Operator | general aviation : corporate |
Make Model Name | Beechjet 400 |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : atp pilot : cfi pilot : instrument |
Experience | flight time last 90 days : 120 flight time total : 4500 flight time type : 700 |
ASRS Report | 631425 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : far non adherence : clearance non adherence : published procedure other anomaly other |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Airport Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were doing a flight to aao on an IFR flight plan in VMC. The flight progressed normally. We idented what we thought was the correct airport (aao). We verified runway alignment and activated the lights on the CTAF. We then told ATC 'airport in sight' and wichita cleared us for a visual and frequency change. We then proceeded with a normal approach and landing to what we thought was jalomar, but was actually bec -- beechfield. We realized our mistake immediately and called approach as soon as we could. Aao and bec are 3 mi apart, have identical runway alignment and the pilot controled lighting is on the same frequency. We approached the area from the south and basically mistook bec for aao. I believe fatigue contributed to the incident as we were at night at this point and were facing a 13 hour 30 min duty cycle. In retrospect, I should have done the IAP to an airport I was not familiar with and had the FMS display 'airports' to see all other airports in the vicinity. In the future, I will not accept a night visual approach to an airport near other airports or a night visual to an airport I am not intentionally familiar with.
Original NASA ASRS Text
Title: BE40 FLT CREW TERMINATES THEIR IFR FLT AFTER VISUALLY ACQUIRING AN ARPT IN THE VICINITY OF THEIR DEST AND LAND AT THE WRONG ARPT.
Narrative: WE WERE DOING A FLT TO AAO ON AN IFR FLT PLAN IN VMC. THE FLT PROGRESSED NORMALLY. WE IDENTED WHAT WE THOUGHT WAS THE CORRECT ARPT (AAO). WE VERIFIED RWY ALIGNMENT AND ACTIVATED THE LIGHTS ON THE CTAF. WE THEN TOLD ATC 'ARPT IN SIGHT' AND WICHITA CLRED US FOR A VISUAL AND FREQ CHANGE. WE THEN PROCEEDED WITH A NORMAL APCH AND LNDG TO WHAT WE THOUGHT WAS JALOMAR, BUT WAS ACTUALLY BEC -- BEECHFIELD. WE REALIZED OUR MISTAKE IMMEDIATELY AND CALLED APCH AS SOON AS WE COULD. AAO AND BEC ARE 3 MI APART, HAVE IDENTICAL RWY ALIGNMENT AND THE PLT CTLED LIGHTING IS ON THE SAME FREQ. WE APCHED THE AREA FROM THE S AND BASICALLY MISTOOK BEC FOR AAO. I BELIEVE FATIGUE CONTRIBUTED TO THE INCIDENT AS WE WERE AT NIGHT AT THIS POINT AND WERE FACING A 13 HR 30 MIN DUTY CYCLE. IN RETROSPECT, I SHOULD HAVE DONE THE IAP TO AN ARPT I WAS NOT FAMILIAR WITH AND HAD THE FMS DISPLAY 'ARPTS' TO SEE ALL OTHER ARPTS IN THE VICINITY. IN THE FUTURE, I WILL NOT ACCEPT A NIGHT VISUAL APCH TO AN ARPT NEAR OTHER ARPTS OR A NIGHT VISUAL TO AN ARPT I AM NOT INTENTIONALLY FAMILIAR WITH.
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.