 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-800 flight crew reported they encroached on the P-56A restricted area when LNAV was mistakenly deselected during departure from dca.
| Attributes | |
| ACN | 1354818 |
| Time | |
| Date | 201605 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | DCA.Airport |
| State Reference | DC |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Pilot Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
On departure; about the same time we received the radio call to switch to departure; I noticed an amber speed lmt annunciation in my pfd. Moments after the call to switch to departure; the copilot called for VNAV. Between switching frequencies and looking for any other indications of a more serious problem; I may have inadvertently pushed LNAV instead of VNAV (disengaging LNAV) which caused the flight director to fly the runway heading and not the SID. By the time the copilot engaged LNAV and turned; we apparently flew into the western edge of P56-a.even though I briefed the warning areas; I briefed them in relation to an engine out event and to plan to go to dulles and maybe should have been more emphatic about not flying into the prohibited airspace in general - to have the nav display in the cross scan until the turn has commenced. Double check that the right button is selected and verified. It's too easy to just fly the flight director.
Original NASA ASRS Text
Title: B737-800 flight crew reported they encroached on the P-56A restricted area when LNAV was mistakenly deselected during departure from DCA.
Narrative: On departure; about the same time we received the radio call to switch to departure; I noticed an amber SPD LMT annunciation in my PFD. Moments after the call to switch to departure; the copilot called for VNAV. Between switching frequencies and looking for any other indications of a more serious problem; I may have inadvertently pushed LNAV instead of VNAV (disengaging LNAV) which caused the flight director to fly the runway heading and not the SID. By the time the copilot engaged LNAV and turned; we apparently flew into the western edge of P56-A.Even though I briefed the warning areas; I briefed them in relation to an engine out event and to plan to go to Dulles and maybe should have been more emphatic about not flying into the prohibited airspace in general - to have the nav display in the cross scan until the turn has commenced. Double check that the right button is selected and verified. It's too easy to just fly the flight director.
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.