37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 263826 |
Time | |
Date | 199402 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : btr |
State Reference | LA |
Altitude | msl bound lower : 700 msl bound upper : 1700 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : btr |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer pilot : atp |
Experience | flight time last 90 days : 177 flight time total : 10389 flight time type : 192 |
ASRS Report | 263826 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 210 flight time total : 4000 flight time type : 700 |
ASRS Report | 263823 |
Events | |
Anomaly | non adherence : published procedure other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | flight crew : became reoriented other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
While on vectors for localizer back course to runway 4L, controller asked if we would like vectors for NDB 13 instead. Thinking we had time to prepare for the approach properly, we accepted. In reality, we were not able to review and prepare for the approach. The controller reported he had a low altitude alert and asked our altitude. This caught us off guard. So he asked again and asked if we knew where we were. We thought we were inside the final fix, when, in reality, we were just outside and were at MDA. He then asked if we saw the field. We did, so he cleared us for the visual approach. By that time the copilot had started a climb back to 1700 ft MSL. The NDB 13 was not in the FMS database but the runway was. When putting the runway as the active waypoint you also get 'FF13.' this we both mistook as the final approach fix, when it is really outside the fix. In the future, I will not accept vectors for another approach unless there is time to fully review the new approach or ask for a radar fix.
Original NASA ASRS Text
Title: MLG ON NDB APCH IS DISORIENTED AND DSNDS TO MDA PRIOR TO FAF.
Narrative: WHILE ON VECTORS FOR LOC BACK COURSE TO RWY 4L, CTLR ASKED IF WE WOULD LIKE VECTORS FOR NDB 13 INSTEAD. THINKING WE HAD TIME TO PREPARE FOR THE APCH PROPERLY, WE ACCEPTED. IN REALITY, WE WERE NOT ABLE TO REVIEW AND PREPARE FOR THE APCH. THE CTLR RPTED HE HAD A LOW ALT ALERT AND ASKED OUR ALT. THIS CAUGHT US OFF GUARD. SO HE ASKED AGAIN AND ASKED IF WE KNEW WHERE WE WERE. WE THOUGHT WE WERE INSIDE THE FINAL FIX, WHEN, IN REALITY, WE WERE JUST OUTSIDE AND WERE AT MDA. HE THEN ASKED IF WE SAW THE FIELD. WE DID, SO HE CLRED US FOR THE VISUAL APCH. BY THAT TIME THE COPLT HAD STARTED A CLB BACK TO 1700 FT MSL. THE NDB 13 WAS NOT IN THE FMS DATABASE BUT THE RWY WAS. WHEN PUTTING THE RWY AS THE ACTIVE WAYPOINT YOU ALSO GET 'FF13.' THIS WE BOTH MISTOOK AS THE FINAL APCH FIX, WHEN IT IS REALLY OUTSIDE THE FIX. IN THE FUTURE, I WILL NOT ACCEPT VECTORS FOR ANOTHER APCH UNLESS THERE IS TIME TO FULLY REVIEW THE NEW APCH OR ASK FOR A RADAR FIX.
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.