37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1606042 |
Time | |
Date | 201812 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | DCA.Airport |
State Reference | DC |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Climb Climb |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
At approximately xa:25 am local time; we pushed off gate at dca. Winds at that time were reporting light and variable. Runway 1 was in use and we thoroughly briefed the departure procedure (including the complex special procedures) at the gate. Upon reaching runway 1 for departure; the tower reported light and variable winds. Neither gusts nor wind shear had been reported. We were cleared for takeoff and proceeded to fly the standard departure procedure with the complex RNAV procedures for runway. The turn to [heading] 332 was initiated at 150 feet AGL. The captain called for 'navigation mode' at 150 feet. I selected navigation. During the initial climb; the aircraft encountered wind shear between approximately 600-1000 feet AGL. (Winds were estimated 40-50 kts). The wind shear warning message displayed. There was no caution message prior. The captain (pilot flying) took corrective action by flying the published windshear escape maneuver. The captain then called for 'autopilot on' and I selected autopilot on. As a result of flying the escape maneuver; the flight director had sequenced to GA/ws mode therefore canceling the previously selected FMS course taking us from adaxe to beble. We noticed this shortly after the windshear recovery was complete at which time we altered course. This occurred just as we were handed off to potomac departure. At that time; I was task saturated. I do not recall if I made the initial check in with departure as our workload was higher than usual. Potomac departure contacted us and asked for us to identify. Following that transmission we informed the controller that we had encountered windshear and were correcting our course. By this time; we had remained right of course enough to penetrate P-56 airspace. Upon contacting washington center; we were told to contact potomac upon landing. The rest of the flight proceeded normally. After parking at gate; the captain contacted potomac approach and was subsequently informed of the deviation.suggestions: though the windshear recovery was successful; I could have been quicker to alert ATC to our situation. I was task saturated at the time of the event but should have been quicker to inform the controller of our situation and subsequent deviation.
Original NASA ASRS Text
Title: CRJ200 flight crew reported an airspace violation shortly after takeoff from DCA due to execution of a windshear escape maneuver.
Narrative: At approximately XA:25 am local time; we pushed off gate at DCA. Winds at that time were reporting light and variable. Runway 1 was in use and we thoroughly briefed the departure procedure (including the complex special procedures) at the gate. Upon reaching Runway 1 for departure; the Tower reported light and variable winds. Neither gusts nor wind shear had been reported. We were cleared for takeoff and proceeded to fly the standard departure procedure with the complex RNAV procedures for runway. The turn to [heading] 332 was initiated at 150 feet AGL. The Captain called for 'NAV MODE' at 150 feet. I selected NAV. During the initial climb; the aircraft encountered wind shear between approximately 600-1000 feet AGL. (Winds were estimated 40-50 kts). The wind shear warning message displayed. There was no caution message prior. The Captain (Pilot Flying) took corrective action by flying the published windshear escape maneuver. The Captain then called for 'autopilot on' and I selected autopilot on. As a result of flying the escape maneuver; the Flight Director had sequenced to GA/WS mode therefore canceling the previously selected FMS course taking us from ADAXE to BEBLE. We noticed this shortly after the windshear recovery was complete at which time we altered course. This occurred just as we were handed off to Potomac Departure. At that time; I was task saturated. I do not recall if I made the initial check in with departure as our workload was higher than usual. Potomac Departure contacted us and asked for us to IDENT. Following that transmission we informed the Controller that we had encountered windshear and were correcting our course. By this time; we had remained right of course enough to penetrate P-56 airspace. Upon contacting Washington center; we were told to contact Potomac upon landing. The rest of the flight proceeded normally. After parking at gate; the Captain contacted Potomac Approach and was subsequently informed of the deviation.Suggestions: Though the windshear recovery was successful; I could have been quicker to alert ATC to our situation. I was task saturated at the time of the event but should have been quicker to inform the controller of our situation and subsequent deviation.
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.