37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1496271 |
Time | |
Date | 201711 |
Local Time Of Day | ZZZ |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Aircraft 1 | |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | SID LADYJ |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 240 Flight Crew Type 12000 |
Person 2 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 157 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
Flying ladyj 2 RNAV departure in VNAV; we allowed aircraft to accelerate to climb speed at 10;000 ft instead of adhering to 250 knot restriction until notified by ATC. Passing approximately 12;000 ft; socal notified us of the airspeed deviation. We pre-briefed the departure and were prepared to comply with the airspeed restriction. As a technique; I will manually place 250 in the 10;000 ft climb to protect airspeed restriction or manually select level change; such as XXX restrictions. I failed to do so this night due to distractions and attempts to get our 'push' clearance. Also; I had expanded the departure page diagram to better see the page at night which actually hid the departure airspeed restriction resulting in a 296 KIAS climb above 10;000 ft.this was nothing more than a typical human factors error. I was distracted out of my habit pattern as we neared our push time waiting for the numbers and excess traffic which occurs around our lax gates. Also; lack of recent flying departures to the north may have caused me to mentally blank the restriction even after I briefed it during preflight. Can the FMC be programmed to comply with such airspeed restrictions as a backup whereby we would be able to select econ when cleared by ATC? It is a published restriction.
Original NASA ASRS Text
Title: B737 Captain and First Officer reported exceeding a speed restriction on departure after reconfiguring their EFB display and inadvertently hiding the published airspeed restriction from view.
Narrative: Flying LADYJ 2 RNAV Departure in VNAV; we allowed aircraft to accelerate to climb speed at 10;000 ft instead of adhering to 250 knot restriction until notified by ATC. Passing approximately 12;000 ft; SoCal notified us of the airspeed deviation. We pre-briefed the departure and were prepared to comply with the airspeed restriction. As a technique; I will manually place 250 in the 10;000 ft climb to protect airspeed restriction or manually select Level Change; such as XXX restrictions. I failed to do so this night due to distractions and attempts to get our 'push' clearance. Also; I had expanded the departure page diagram to better see the page at night which actually hid the departure airspeed restriction resulting in a 296 KIAS climb above 10;000 ft.This was nothing more than a typical human factors error. I was distracted out of my habit pattern as we neared our push time waiting for the numbers and excess traffic which occurs around our LAX gates. Also; lack of recent flying departures to the north may have caused me to mentally blank the restriction even after I briefed it during preflight. Can the FMC be programmed to comply with such airspeed restrictions as a backup whereby we would be able to select ECON when cleared by ATC? It is a published restriction.
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.