37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1059680 |
Time | |
Date | 201301 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZLA.ARTCC |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Flying First Officer |
Experience | Flight Crew Last 90 Days 98 Flight Crew Total 7600 Flight Crew Type 300 |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
After receiving a clearance to 'descend via seavu arrival cleared for the approach; maintain 280 knots' the captain didn't set MCP altitude and I failed to catch it. ATC called us back in approximately two minutes and asked if we had started down. We realized the mistake and attempted to comply with the clearance but slowed below assigned airspeed due to VNAV built in speed reduction; which we corrected immediately after which we received no further word from the controller. There were no altitude busts; just a slight reduction below assigned speed. The arrival had been briefed thoroughly for what we expected and what was given. Event was simply a mistake we attributed to unfamiliar new MCP procedures. A contributing factor was a heavier than usual workload environment due to monitoring fuel management to avoid an over weight landing. We tankered fuel from iah. We requested a lower altitude at approximately phx to comply with landing weight.
Original NASA ASRS Text
Title: A B737 flight crew suffered modest deviations while performing the SEAVU STAR to LAX while utilizing new company Mode Control Panel SOPs.
Narrative: After receiving a clearance to 'descend via Seavu arrival cleared for the approach; maintain 280 knots' the Captain didn't set MCP altitude and I failed to catch it. ATC called us back in approximately two minutes and asked if we had started down. We realized the mistake and attempted to comply with the clearance but slowed below assigned airspeed due to VNAV built in speed reduction; which we corrected immediately after which we received no further word from the Controller. There were no altitude busts; just a slight reduction below assigned speed. The arrival had been briefed thoroughly for what we expected and what was given. Event was simply a mistake we attributed to unfamiliar new MCP procedures. A contributing factor was a heavier than usual workload environment due to monitoring fuel management to avoid an over weight landing. We tankered fuel from IAH. We requested a lower altitude at approximately PHX to comply with landing weight.
Data retrieved from NASA's ASRS site as of July 2013 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.