 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A320 captain reported missing an altitude restriction on arrival into iah; citing a late runway change as contributing.
| Attributes | |
| ACN | 1618536 |
| Time | |
| Date | 201902 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | IAH.Airport |
| State Reference | TX |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Undershoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
First off; I don't think it is possible to properly brief for multiple runway assignments; especially when there are notams involved for each runway. Along with being informed late by ATC. Runway 27 was the last runway I would expect while on this arrival. The expected runway via the arrival is 26R. Me underlining the NOTAM for 27 did not help me to remember unfortunately. Switching the runway up is busy enough work in this phase of flight. I'll be more aware of this type of goat rope by ATC as a possibility after this incident. Next up. ATC giving a visual clearance with a crossing restriction over a fix that is only on the ILS 27 and RNAV approach plate. This to me is a very lousy clearance. That being said; I accepted the clearance. So I take some blame. At the same time ATC needs to refrain from giving such clearances. Last minute runway switches can be very troublesome especially when notams are involved. I'm not sure why the ATIS did not advertise runway 27 RNAV instead of the visual. Both runway 26R and 26L were shown on the ATIS as both ILS approaches. Had this been the case (RNAV 27 approach advertised) none of this would have happened. I know I am the last line of defense and I did catch these errors; unfortunately not as quick as I would have liked to. But it would help if the system was better set up to not set the pilots on such course.
Original NASA ASRS Text
Title: A320 Captain reported missing an altitude restriction on arrival into IAH; citing a late runway change as contributing.
Narrative: First off; I don't think it is possible to properly brief for multiple runway assignments; especially when there are NOTAMs involved for each runway. Along with being informed late by ATC. Runway 27 was the last runway I would expect while on this arrival. The expected runway via the arrival is 26R. Me underlining the NOTAM for 27 did not help me to remember unfortunately. Switching the runway up is busy enough work in this phase of flight. I'll be more aware of this type of goat rope by ATC as a possibility after this incident. Next up. ATC giving a visual clearance with a crossing restriction over a fix that is only on the ILS 27 and RNAV approach plate. This to me is a very lousy clearance. That being said; I accepted the clearance. So I take some blame. At the same time ATC needs to refrain from giving such clearances. Last minute runway switches can be very troublesome especially when NOTAMs are involved. I'm not sure why the ATIS did not advertise Runway 27 RNAV instead of the visual. Both Runway 26R and 26L were shown on the ATIS as both ILS approaches. Had this been the case (RNAV 27 approach advertised) none of this would have happened. I know I am the last line of defense and I did catch these errors; unfortunately not as quick as I would have liked to. But it would help if the system was better set up to not set the pilots on such course.
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.