37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1093055 |
Time | |
Date | 201306 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Challenger 300 |
Operating Under FAR Part | Part 135 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Critical |
Narrative:
While at cruise erroneous EICAS messages started to appear on the message board. The messages would post for a few second and then disappear. Red; amber; and cyan messages were being displayed. Messages included pylon bleed-leak; engine fire; spoiler deployed; etc. Spoiler fault displayed red on the synoptic page. The messages continued to display throughout the rest of the flight. Sometimes many messages and other times just a few. Next we noticed the navigation frequencies flip flopping uncommanded. Comm 2 was going reversionary to the flying pilots pfd. All frequencies were turning from amber to green and back to amber. Multiple transmissions were required to communicate with center because the comm frequencies would switch after a few seconds and then drop out. At this point the captain called dispatch from the sat phone to explain the situation and have then contact the TRACON. He also spoke to maintenance control to troubleshoot the problem. After troubleshooting with maintenance there wasn't a fix. We decided to continue to the destination where the weather was reported 10;000 ft overcast. The rest of the flight we continued to work the radios to maintain our frequencies and communicate with center. We descended below the clouds and had visual contact with [the airport]. Approach control cleared us for a visual approach. We canceled IFR on the ground in [the airport].this event was unavoidable. We should have followed updated bombardier procedures to tune 121.5 on the reversionary panel.
Original NASA ASRS Text
Title: Despite multiple; apparently erroneous; EICAS messages and malfunctioning communications radios the flight crew of a CL-300 elected to continue and complete their three hour IFR flight.
Narrative: While at cruise erroneous EICAS messages started to appear on the message board. The messages would post for a few second and then disappear. Red; Amber; and Cyan messages were being displayed. Messages included pylon bleed-leak; engine fire; spoiler deployed; etc. Spoiler fault displayed red on the synoptic page. The messages continued to display throughout the rest of the flight. Sometimes many messages and other times just a few. Next we noticed the NAV frequencies flip flopping uncommanded. COMM 2 was going reversionary to the flying pilots PFD. All frequencies were turning from amber to green and back to amber. Multiple transmissions were required to communicate with Center because the COMM frequencies would switch after a few seconds and then drop out. At this point the Captain called Dispatch from the SAT phone to explain the situation and have then contact the TRACON. He also spoke to Maintenance Control to troubleshoot the problem. After troubleshooting with Maintenance there wasn't a fix. We decided to continue to the destination where the weather was reported 10;000 FT overcast. The rest of the flight we continued to work the radios to maintain our frequencies and communicate with Center. We descended below the clouds and had visual contact with [the airport]. Approach Control cleared us for a visual approach. We canceled IFR on the ground in [the airport].This event was unavoidable. We should have followed updated Bombardier procedures to tune 121.5 on the reversionary panel.
Data retrieved from NASA's ASRS site as of July 2013 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.