37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1510060 |
Time | |
Date | 201801 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SNA.Airport |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | SID FINZZ2 |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 150 Flight Crew Type 7500 |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance |
Narrative:
We were flying the finzz 2 SID out of sna. We were given a vector off the SID and told to maintain 8000 and expect direct cahil. Shortly thereafter; we were cleared direct to finzz and also instructed to climb via the SID. I did not hear the climb via clearance. I was expecting to receive a clearance direct to cahil. When we received a clearance to finzz I referenced the SID on my efb. I believe referencing the efb distracted me just enough to miss the climb via portion of the radio call. Enroute to finzz; the first officer; who was pm; said we were given a climb via clearance. I asked the first officer to confirm our climb clearance with socal; which he did. Socal; confirmed we were cleared to climb via the SID; so I immediately began a climb to the finzz crossing restriction of at or above 10;000. Complying with the at or above 10;000 restriction at this point would have been tough. Socal immediately vectored us off the SID for our climb. The first error I made was missing the climb via clearance. I was expecting to receive a clearance direct to cahil. When we received the clearance to finzz I distracted myself by referencing the SID on my efb at an inopportune time. The first officer had correctly understood the climb via clearance; but by the time we got the confirmation from socal we were coming up on finzz. If our crew communication had been timelier; we could have trapped the error sooner and complied with our clearance. We had reviewed the SID on the ground so I should have simply made the input into the FMC and MCP. Correctly prioritizing tasks would have trapped this error.
Original NASA ASRS Text
Title: B737 Captain reported missing a 'climb via' clearance on the FINZZ2 SID out of SNA due to a cockpit distraction.
Narrative: We were flying the FINZZ 2 SID out of SNA. We were given a vector off the SID and told to maintain 8000 and expect direct CAHIL. Shortly thereafter; we were cleared direct to FINZZ and also instructed to climb via the SID. I did not hear the climb via clearance. I was expecting to receive a clearance direct to CAHIL. When we received a clearance to FINZZ I referenced the SID on my EFB. I believe referencing the EFB distracted me just enough to miss the climb via portion of the radio call. Enroute to FINZZ; the FO; who was PM; said we were given a climb via clearance. I asked the FO to confirm our climb clearance with SoCal; which he did. SoCal; confirmed we were cleared to climb via the SID; so I immediately began a climb to the FINZZ crossing restriction of at or above 10;000. Complying with the at or above 10;000 restriction at this point would have been tough. SoCal immediately vectored us off the SID for our climb. The first error I made was missing the climb via clearance. I was expecting to receive a clearance direct to CAHIL. When we received the clearance to FINZZ I distracted myself by referencing the SID on my EFB at an inopportune time. The FO had correctly understood the climb via clearance; but by the time we got the confirmation from SoCal we were coming up on FINZZ. If our Crew communication had been timelier; we could have trapped the error sooner and complied with our clearance. We had reviewed the SID on the ground so I should have simply made the input into the FMC and MCP. Correctly prioritizing tasks would have trapped this error.
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.