37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1223316 |
Time | |
Date | 201412 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ORD.Airport |
State Reference | IL |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B747 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
ATIS calling visual approaches for [runway] 28C. Pilot flying (PF) briefed the ILS runway 28C. Upon PF request tower told us to expect ILS 28R and subsequently PF briefed ILS 28R. The flight was cleared to descend and maintain 4000 feet and at that altitude to intercept localizer 28R. While at 4000 feet on the localizer 28R we were then cleared for the ILS 28R and to report a 5 mile final. While I (pilot monitoring) was looking out for traffic the PF set 2200 feet in the altitude window (glideslope intercept altitude) and pushed flight level change without making me aware of the MCP changes. Tower notified us to check our altitude and gave us an altimeter setting of 30.38 in qnh because he showed us at 2300 feet. I then confirmed to tower our altitude and qnh. Tower said that we appeared low and asked if we had the runway 28R in sight. We confirmed that the runway was in sight and PF initiated and immediate climb towards 4000 feet. Ultimately intercepted glideslope at 3000 feet and landed normally. The PF apologized to the tower controller for his improper altitude and he said in effect 'no problem; just wanted to make sure everything was okay'. Adhering to company SOP's regarding MCP changes would have prevented this from happening.
Original NASA ASRS Text
Title: B747 First Officer as Pilot Monitoring reports his Captain descending to the glideslope intercept altitude of 2;200 feet well before the ILS procedure allows descent below 4;000 feet. The reporter was looking for traffic and did not notice the descent. The Tower called the low altitude resulting in a climb to 3;000 feet to intercept the glideslope.
Narrative: ATIS calling visual approaches for [Runway] 28C. Pilot flying (PF) briefed the ILS Runway 28C. Upon PF request Tower told us to expect ILS 28R and subsequently PF briefed ILS 28R. The flight was cleared to descend and maintain 4000 feet and at that altitude to intercept LOC 28R. While at 4000 feet on the LOC 28R we were then cleared for the ILS 28R and to report a 5 mile final. While I (Pilot Monitoring) was looking out for traffic the PF set 2200 feet in the altitude window (Glideslope intercept altitude) and pushed Flight Level Change without making me aware of the MCP changes. Tower notified us to check our altitude and gave us an altimeter setting of 30.38 in QNH because he showed us at 2300 feet. I then confirmed to tower our altitude and QNH. Tower said that we appeared low and asked if we had the runway 28R in sight. We confirmed that the runway was in sight and PF initiated and immediate climb towards 4000 feet. Ultimately intercepted glideslope at 3000 feet and landed normally. The PF apologized to the tower controller for his improper altitude and he said in effect 'no problem; just wanted to make sure everything was okay'. Adhering to Company SOP's regarding MCP changes would have prevented this from happening.
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.