 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew reported that the first officer experienced erroneous airspeed indications while flying through heavy rain.
| Attributes | |
| ACN | 1469614 |
| Time | |
| Date | 201707 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Pitot-Static System |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 46 |
| Person 2 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Deviation - Speed All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
As pilot flying; we were navigating around moderate to heavy precipitation using heading select and climbing to FL330 using VNAV. During the climb; I realized I had bad air data; as the airspeed suddenly displayed in the 130 knot range along with other erroneous readouts. At the same time I was trying to diagnose the situation; the captain noticed the autopilot had commanded a descent. Realizing my computer was receiving bad data; controls were quickly transferred to the captain; who turned off the automation and began to hand fly. In regaining positive aircraft control; our flight altitude reached 33;100 ft; but simultaneously we were also given a new heading and altitude clearance of FL390. The autopilot was commanded back on and the flight continued a normal climb using the captain-side air data. During the climb; we discussed the situation and determined the first officer static port had iced over and caused my computer to display wrong information. The system returned to normal once clear of the precipitation; and the aircraft control was later returned to the first officer side after verifying read outs on both sides corresponded with each other.
Original NASA ASRS Text
Title: B737 flight crew reported that the First Officer experienced erroneous airspeed indications while flying through heavy rain.
Narrative: As Pilot Flying; we were navigating around moderate to heavy precipitation using heading select and climbing to FL330 using VNAV. During the climb; I realized I had bad air data; as the airspeed suddenly displayed in the 130 knot range along with other erroneous readouts. At the same time I was trying to diagnose the situation; the Captain noticed the autopilot had commanded a descent. Realizing my computer was receiving bad data; controls were quickly transferred to the Captain; who turned off the automation and began to hand fly. In regaining positive aircraft control; our flight altitude reached 33;100 ft; but simultaneously we were also given a new heading and altitude clearance of FL390. The autopilot was commanded back on and the flight continued a normal climb using the Captain-side air data. During the climb; we discussed the situation and determined the First Officer static port had iced over and caused my computer to display wrong information. The system returned to normal once clear of the precipitation; and the aircraft control was later returned to the First Officer side after verifying read outs on both sides corresponded with each other.
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.