37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1403692 |
Time | |
Date | 201611 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PHL.Tower |
State Reference | PA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial 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 | Inflight Event / Encounter Weather / Turbulence |
Narrative:
We received a wind shear alert on our departure climb. Previously at the gate we had briefed the low level wind shear considerations which was posted in the ATIS. [The first officer] was flying the leg departing 27R and at approximately 1000 ft AGL we received the wind shear warning. I assisted [the first officer] in the wind shear maneuver calling for max thrust and no configuration changes to the aircraft. The warning lasted through 1500 ft AGL at which point it went away; due to wind shear detection stopping at this altitude. We maintained no configuration changes for another several hundred feet until we verified a positive airspeed trend vector in addition to the climbing altitude. At this point we cleaned up the aircraft and [performed] after takeoff checks.at takeoff we had been issued a left turn to heading 230; which we initially began at 400 ft AGL; however stopped turn at approximately 250 degrees when the wind shear 'GA/ws' mode became active and gave us a heading sync. After we were clear of the wind shear we resumed the turn to 230 degrees and leveled at our top of climb 5000 feet; and I informed ATC of the wind shear event. During the event I didn't notice a decreasing performance in airspeed; yet there didn't seem to be an increasing trend vector either; which I believe this stagnation may have triggered the alert.
Original NASA ASRS Text
Title: CRJ-200 flight crew reported compliance with a wind shear alert departing PHL.
Narrative: We received a wind shear alert on our departure climb. Previously at the gate we had briefed the low level wind shear considerations which was posted in the ATIS. [The First Officer] was flying the leg departing 27R and at approximately 1000 ft AGL we received the wind shear warning. I assisted [the First Officer] in the wind shear maneuver calling for max thrust and no configuration changes to the aircraft. The warning lasted through 1500 ft AGL at which point it went away; due to wind shear detection stopping at this altitude. We maintained no configuration changes for another several hundred feet until we verified a positive airspeed trend vector in addition to the climbing altitude. At this point we cleaned up the aircraft and [performed] after takeoff checks.At takeoff we had been issued a left turn to heading 230; which we initially began at 400 ft AGL; however stopped turn at approximately 250 degrees when the wind shear 'GA/WS' mode became active and gave us a heading sync. After we were clear of the wind shear we resumed the turn to 230 degrees and leveled at our top of climb 5000 feet; and I informed ATC of the wind shear event. During the event I didn't notice a decreasing performance in airspeed; yet there didn't seem to be an increasing trend vector either; which I believe this stagnation may have triggered the alert.
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.