37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1178917 |
Time | |
Date | 201406 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Aircraft 1 | |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
There was no report on if this problem had been written up before or if the leak developed after the 'a' check. Continuing to destination was an option.weather had gone below VMC at lax and socal was busy on the radio creating greater separation for the flights arriving at lax. While descending to FL240 in a holding pattern at jli; we were cleared to proceed direct to jli to fly the vista 2 arrival; cross cynde at 12;000 and continue via the vista 2 arrival. We had programmed the expected altitudes in the FMC and mistakenly interpreted the ATC clearance as to; 'cross cynde at 12;000 and descend via the vista arrival.' during the descent to 12;000; we were handed off to socal; and I believe I reported that we were [descending] to cross cynde at 12;000 and continue via the vista 2 arrival. Since we were in VNAV path; we mistakenly put the last expected altitude in the altitude window (7;000) and after crossing cynde; we continued on the VNAV path; below 12;000. About 11;600 ft socal asked what our altitude clearance was. We replied; to cross cynde at 12;000 and descend via the vista. Socal replied; 'descend and maintain 10;000.' about a minute later; socal advised the vista arrival only has expected altitudes and we were not cleared to ''descend' via the vista arrival.' socal said no loss of separation occurred and no paperwork was being filed by them. When briefing arrival and approaches [I will] make a distinction between published altitudes and expected altitudes. When expected altitudes exist on the arrival; I won't mistake them for published altitudes.
Original NASA ASRS Text
Title: A B737NG flight crew misinterpreted Center's clearance to '...leave a holding pattern direct to JLI and continue via the VISTA STAR; cross CYNDE at 12;000 FT to mean 'descend via' the STAR. Shortly after passing CYNDE and continuing their descent ATC advised that all altitudes on the STAR were 'expect to cross' and they had not been cleared below 12;000.
Narrative: There was no report on if this problem had been written up before or if the leak developed after the 'A' check. Continuing to destination was an option.Weather had gone below VMC at LAX and SoCal was busy on the radio creating greater separation for the flights arriving at LAX. While descending to FL240 in a holding pattern at JLI; we were cleared to proceed direct to JLI to fly the VISTA 2 Arrival; cross CYNDE at 12;000 and continue via the VISTA 2 Arrival. We had programmed the expected altitudes in the FMC and mistakenly interpreted the ATC clearance as to; 'Cross CYNDE at 12;000 and descend VIA the VISTA Arrival.' During the descent to 12;000; we were handed off to SoCal; and I believe I reported that we were [descending] to cross CYNDE at 12;000 and continue via the VISTA 2 Arrival. Since we were in VNAV PATH; we mistakenly put the last expected altitude in the Altitude Window (7;000) and after crossing CYNDE; we continued on the VNAV path; below 12;000. About 11;600 FT SoCal asked what our altitude clearance was. We replied; to cross CYNDE at 12;000 and descend via the VISTA. SoCal replied; 'Descend and maintain 10;000.' About a minute later; SoCal advised the VISTA Arrival only has expected altitudes and we were not cleared to ''descend' VIA the VISTA Arrival.' SoCal said no loss of separation occurred and no paperwork was being filed by them. When briefing arrival and approaches [I will] make a distinction between published altitudes and expected altitudes. When expected altitudes exist on the arrival; I won't mistake them for published altitudes.
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.