37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1611445 |
Time | |
Date | 201901 |
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 | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | Pitot-Static System |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical Inflight Event / Encounter Weather / Turbulence |
Narrative:
While on approach we encountered icing conditions on the approach. Warning system started going off. Approach asked us to slow multiple times but since unreliable airspeed was on captain's side we were correcting airspeeds on his side then started getting more bells. We started to complete QRH but we were being directed at the same time trying to figure out which side was correct. We informed approach on the problem and completed verification of the problem side. We transferred controls to first officer side and completed the approach and landing with no further issues. Threat icing conditions; threats close proximity on approach to final approach fix; threat trying to run QRH and verifying good side while on close final; threat airspeed indicating 160 and really doing 260. [Lesson] learned from this would be to cancel approach clearance; get vector heading and work the problem with more time and the controller not yacking in your ear continuously after making him aware of our discrepancy in airspeed; and him to continue to issue slower speeds to us; while continuing the approach.
Original NASA ASRS Text
Title: CRJ-200 First Officer reported icing conditions resulted in Captain's airspeed indicator errors.
Narrative: While on approach we encountered icing conditions on the approach. Warning system started going off. Approach asked us to slow multiple times but since unreliable airspeed was on Captain's side we were correcting airspeeds on his side then started getting more bells. We started to complete QRH but we were being directed at the same time trying to figure out which side was correct. We informed Approach on the problem and completed verification of the problem side. We transferred controls to FO side and completed the approach and landing with no further issues. Threat icing conditions; Threats close proximity on approach to final approach fix; Threat trying to run QRH and verifying good side while on close final; Threat airspeed indicating 160 and really doing 260. [Lesson] learned from this would be to cancel approach clearance; get vector heading and work the problem with more time and the controller not yacking in your ear continuously after making him aware of our discrepancy in airspeed; and him to continue to issue slower speeds to us; while continuing the approach.
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.