37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 81659 |
Time | |
Date | 198801 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : eli airport : egi |
State Reference | FL |
Altitude | agl bound lower : 1500 agl bound upper : 1500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : cew tower : egi |
Operator | other |
Make Model Name | Military Transport |
Flight Phase | descent : approach landing : go around |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : military |
Function | flight crew : first officer |
Qualification | pilot : military |
Experience | flight time last 90 days : 30 flight time total : 3000 |
ASRS Report | 81659 |
Person 2 | |
Function | flight crew : captain oversight : pic |
Qualification | pilot : military |
Events | |
Anomaly | incursion : runway non adherence : far other anomaly other other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
While on a sortie from dobbins AFB, GA, to duke field (elgin auxiliary field #3), our aircraft (mlt) incorrectly identified crestview airport as duke field and nearly landed there. We flew in crestview's airspace west/O clearance. We discovered the problem on a 2 mi final that we were not lined up for duke, but for crestview (crestview is 10 NM north of duke). It was the crew that made the discovery. We turned eastbound, climbed, and continued to duke field. At no time did we contact crestview tower, as we were taking to duke tower and thought we had duke in sight. What caused the problem: inadequate permission planning, failure to use all available navaids (we plotted a radial/DME fix from crestview to identify duke, but did not take it in. The aircraft was equipped with INS but was not programmed with duke coordinates), early cancellation of IFR flight plan (crew cancelled IFR clearance approximately 15-20 mi north of crestview west/O duke in sight), and elgin approach control was contacted inbound to duke, but they provided no assistance when we reported field in sight (wrong field) and then switched us to duke tower.
Original NASA ASRS Text
Title: MLT WRONG ARPT APCH.
Narrative: WHILE ON A SORTIE FROM DOBBINS AFB, GA, TO DUKE FIELD (ELGIN AUX FIELD #3), OUR ACFT (MLT) INCORRECTLY IDENTIFIED CRESTVIEW ARPT AS DUKE FIELD AND NEARLY LANDED THERE. WE FLEW IN CRESTVIEW'S AIRSPACE W/O CLRNC. WE DISCOVERED THE PROB ON A 2 MI FINAL THAT WE WERE NOT LINED UP FOR DUKE, BUT FOR CRESTVIEW (CRESTVIEW IS 10 NM N OF DUKE). IT WAS THE CREW THAT MADE THE DISCOVERY. WE TURNED EBND, CLBED, AND CONTINUED TO DUKE FIELD. AT NO TIME DID WE CONTACT CRESTVIEW TWR, AS WE WERE TAKING TO DUKE TWR AND THOUGHT WE HAD DUKE IN SIGHT. WHAT CAUSED THE PROBLEM: INADEQUATE PERMISSION PLANNING, FAILURE TO USE ALL AVAILABLE NAVAIDS (WE PLOTTED A RADIAL/DME FIX FROM CRESTVIEW TO IDENTIFY DUKE, BUT DID NOT TAKE IT IN. THE ACFT WAS EQUIPPED WITH INS BUT WAS NOT PROGRAMMED WITH DUKE COORDINATES), EARLY CANCELLATION OF IFR FLT PLAN (CREW CANCELLED IFR CLRNC APPROX 15-20 MI N OF CRESTVIEW W/O DUKE IN SIGHT), AND ELGIN APCH CTL WAS CONTACTED INBND TO DUKE, BUT THEY PROVIDED NO ASSISTANCE WHEN WE RPTED FIELD IN SIGHT (WRONG FIELD) AND THEN SWITCHED US TO DUKE TWR.
Data retrieved from NASA's ASRS site as of August 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.