 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-700 flight crew reported failing to make a crossing restriction on the rnp-Z runway 20R approach to sna.
| Attributes | |
| ACN | 1574675 |
| Time | |
| Date | 201808 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | SNA.Airport |
| State Reference | CA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying First Officer |
| Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 175 Flight Crew Type 1900 |
| Person 2 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 357 |
| Events | |
| Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Undershoot Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
Sna rnp-Z to runway 20R. The FMC was properly programmed and MCP panel [was] in LNAV/VNAV path. Upon crossing klevr at 5000 ft IAF; we set zeros in the altitude alerter. The aircraft did not descend to cross mnnie at 4400 ft; next mandatory altitude. I noticed level flight and immediately selected vertical speed to try and meet mnnie at 4400 feet. About the same time; socal approach asked us if we were descending and flying the rnp-Z. The pilot monitoring (pm) said 'yes' but asked if we could be cleared the visual approach to try and mitigate any problems. Socal said 'no problem' and gave us a 'heading of 030 and descend to 3000 ft; call the field in sight.' as pilot flying (PF); the field was on my side and we had it in sight and called - in sight. At that point we were cleared for the visual and told to contact sna tower. The rest of the approach and landing were uneventful and we landed safely on 20R. With short distances between waypoints and mandatory descending altitude restrictions; pilots should be quicker to notice any anomaly and react quickly to stay in/on VNAV path even if aircraft does not do it automatically.
Original NASA ASRS Text
Title: B737-700 flight crew reported failing to make a crossing restriction on the RNP-Z Runway 20R approach to SNA.
Narrative: SNA RNP-Z to Runway 20R. The FMC was properly programmed and MCP panel [was] in LNAV/VNAV PATH. Upon crossing KLEVR at 5000 FT IAF; we set zeros in the altitude alerter. The aircraft did not descend to cross MNNIE at 4400 FT; next mandatory altitude. I noticed level flight and immediately selected Vertical Speed to try and meet MNNIE at 4400 feet. About the same time; SoCal Approach asked us if we were descending and flying the RNP-Z. The Pilot Monitoring (PM) said 'yes' but asked if we could be cleared the Visual Approach to try and mitigate any problems. SoCal said 'no problem' and gave us a 'heading of 030 and descend to 3000 FT; call the field in sight.' As Pilot Flying (PF); the field was on my side and we had it in sight and called - in sight. At that point we were cleared for the visual and told to contact SNA Tower. The rest of the approach and landing were uneventful and we landed safely on 20R. With short distances between waypoints and mandatory descending altitude restrictions; pilots should be quicker to notice any anomaly and react quickly to stay in/on VNAV PATH even if aircraft does not do it automatically.
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.