37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 858227 |
Time | |
Date | 200910 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | DFW.Airport |
State Reference | TX |
Environment | |
Flight Conditions | Mixed |
Light | Night |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | Weather Radar |
Person 1 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Speed All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
A dark and stormy night. Autopilot engaged. Captain flying RNAV departure...electing to use terrain display because I had selected weather. I could see thunderstorms in departure path - not rain - clear cut line of cells -and had to draw his attention to it because he was not displaying weather. At one point we nicked the edge of a cell; along with some real big bumps. We were way to close to the big red blobs. In maneuvering to clear the weather; the captain neglected to call for slat retraction. Since I was nervous about the 'weather avoidance' strategy and was closely monitoring the flight path. I did not complete the climb checklist; I became absorbed in the weather situation; and I did not notice slat extended. At 280 KTS 'slat overspeed' sounded. One day later I checked the maintenance record to see what the corrective action was needed and I could find no record of the slat overspeed logged in the maintenance computer; even though the captain wrote it up. Looks like it just disappeared. Recommendation - if there is weather in the departure area both pilots should be required to display; brief; and avoid the weather. Having terrain displayed is of no value over flat areas; and terrain will 'pop up' if a conflict is detected anyway. We should both be looking at the real threat in any given situation; and these 50;000 ft texas thunderstorms can be a real threat.
Original NASA ASRS Text
Title: An air carrier pilot reported that Company policy required one pilot to display Terrain while the other pilot displayed Weather. If weather is present but terrain is flat; both pilots should be in weather for proper avoidance and discussion.
Narrative: A dark and stormy night. Autopilot engaged. Captain flying RNAV departure...electing to use Terrain display because I had selected weather. I could see thunderstorms in departure path - not rain - clear cut line of cells -and had to draw his attention to it because he was not displaying weather. At one point we nicked the edge of a cell; along with some real big bumps. We were way to close to the Big Red Blobs. In maneuvering to clear the weather; the Captain neglected to call for slat retraction. Since I was nervous about the 'weather avoidance' strategy and was closely monitoring the flight path. I did not complete the climb checklist; I became absorbed in the weather situation; and I did not notice slat extended. At 280 KTS 'slat overspeed' sounded. One day later I checked the maintenance record to see what the corrective action was needed and I could find no record of the slat overspeed logged in the maintenance computer; even though the Captain wrote it up. Looks like it just disappeared. Recommendation - If there is weather in the departure area both pilots should be required to display; brief; and avoid the weather. Having Terrain displayed is of no value over flat areas; and Terrain will 'pop up' if a conflict is detected anyway. We should both be looking at the real threat in any given situation; and these 50;000 FT Texas thunderstorms can be a real threat.
Data retrieved from NASA's ASRS site as of April 2012 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.