37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 838843 |
Time | |
Date | 200906 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | MCO.Airport |
State Reference | FL |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Widebody Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Check Pilot Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 120 Flight Crew Total 10700 Flight Crew Type 1500 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
First officer student was pilot flying. I as check airman/oe instructor was pilot monitoring. Basic set-up is ILS 18R with thunderstorm moving onto field. I'd asked ATC if people were getting in - they said yes; the cell was east of the field and moving east-southeast thereby making the final approach corridor free of the rain/wind that had been reported earlier. The approach was mostly VMC but as we approached the runway complex was IMC with rain. Mco approach typically will ask you to cross over orlando executive airport at 2300 or 2500 MSL. That altitude is above glideslope altitude for the approach. It requires pilots to capture the glideslope from above. I briefed the student en-route about the necessity to be fully configured prior to crossing over orl in order to capture the glideslope. The student configured somewhat late but was on speed and configured but was fixated on being a little behind and did not see the autopilot go into altitude capture at 2300. We were now leveling off above the glideslope. I directed him to disconnect the autopilot and pitch down. He did this. Meanwhile; I was concerned about the cell moving onto the airport and asked ATC for winds and any LLWS advisories. This distracted me from monitoring the approach. Tower then issued a windshear advisory. Meanwhile; the student descended through the glideslope and at approximately 1600 ft mco tower called with 'low altitude warning - check your altitude' we were 1.5 dots low on glideslope. I directed the student to go-around. We landed uneventfully on 36R since mco had switched runways.
Original NASA ASRS Text
Title: First Officer receiving IOE training gets behind aircraft during ILS approach to 18R at MCO. With the instructor distracted by weather; the First Officer got low triggering a low altitude warning from the tower resulting in a go-around.
Narrative: First Officer student was Pilot Flying. I as Check Airman/OE Instructor was Pilot Monitoring. Basic set-up is ILS 18R with thunderstorm moving onto field. I'd asked ATC if people were getting in - they said yes; the cell was east of the field and moving east-southeast thereby making the final approach corridor free of the rain/wind that had been reported earlier. The approach was mostly VMC but as we approached the runway complex was IMC with rain. MCO approach typically will ask you to cross over Orlando Executive airport at 2300 or 2500 MSL. That altitude is above glideslope altitude for the approach. It requires pilots to capture the glideslope from above. I briefed the student en-route about the necessity to be fully configured prior to crossing over ORL in order to capture the glideslope. The student configured somewhat late but was on speed and configured but was fixated on being a little behind and did not see the autopilot go into altitude capture at 2300. We were now leveling off above the glideslope. I directed him to disconnect the autopilot and pitch down. He did this. Meanwhile; I was concerned about the cell moving onto the airport and asked ATC for winds and any LLWS advisories. This distracted me from monitoring the approach. Tower then issued a windshear advisory. Meanwhile; the student descended through the glideslope and at approximately 1600 FT MCO Tower called with 'low altitude warning - check your altitude' We were 1.5 dots low on glideslope. I directed the student to go-around. We landed uneventfully on 36R since MCO had switched runways.
Data retrieved from NASA's ASRS site as of April 2012 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.