37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1586752 |
Time | |
Date | 201810 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZZ.ARTCC |
State Reference | FO |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
During the descent to mroc I thought we were too high; I notice I had entered 16;000 feet instead of 160 knots in the FMC. I asked the first officer (first officer) what is the charted crossing altitude he said 8;000 feet. I know at that point there was no way we could continue the approach. Gear was down; flaps 30 and on the localizer. I told the first officer to tell the tower that we want to orbit 360 (rh turn) at zzzzz (8000 feet) because we were too high. No immediate reply from the tower; so I began the rh turn. First officer joined me on taws and we were cleared to join the approach and report on the loc. We then flew direct to zzzzz and the approach was normal. The weather was IMC we descended below the minimum radar vectoring altitude prior to joining the localizer. I accept responsibility for the decision to turn and should have continued straight ahead and ask for radar vectors to for another ILS approach. We were under no time pressure as we had more than enough fuel. The problems with automation was triggered by the intended 160 knot entry triggered 16;000 foot crossing instead. Check and recheck the FMC; and get first officer to check for errors. Brief a plan of action in case too high. Tell ATC we are too high; request radar victors to rejoin the approach.
Original NASA ASRS Text
Title: B767 Captain reported flight crew failed to properly load the FMS. While rejoining the final approach course the crew descended below the minimum vectoring altitude.
Narrative: During the descent to MROC I thought we were too high; I notice I had entered 16;000 feet instead of 160 knots in the FMC. I asked the First Officer (FO) what is the charted crossing altitude he said 8;000 feet. I know at that point there was no way we could continue the approach. Gear was down; Flaps 30 and on the LOC. I told the FO to tell the Tower that we want to orbit 360 (RH Turn) at ZZZZZ (8000 feet) because we were too high. No immediate reply from the Tower; so I began the RH turn. FO joined me on TAWS and we were cleared to join the approach and report on the loc. We then flew direct to ZZZZZ and the approach was normal. The weather was IMC we descended below the minimum radar vectoring altitude prior to joining the LOC. I accept responsibility for the decision to turn and should have continued straight ahead and ask for radar vectors to for another ILS approach. We were under no time pressure as we had more than enough fuel. The problems with automation was triggered by the intended 160 knot entry triggered 16;000 foot crossing instead. Check and recheck the FMC; and get FO to check for errors. Brief a plan of action in case too high. Tell ATC we are too high; request radar victors to rejoin the approach.
Data retrieved from NASA's ASRS site 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.