 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Bombardier challenger first officer reported receiving multiple EICAS messages indicating faults for various systems.
| Attributes | |
| ACN | 1473383 |
| Time | |
| Date | 201708 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.ARTCC |
| State Reference | US |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Challenger 350 |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Squat Switch |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
I was the PF on [this flight]. While at cruise we started receiving multiple cyan EICAS messages. They read spoiler fault; lt engine fault; rt engine fault; proximity system fault; stabilizer trim fault. We then got a yellow wow fault yellow caution msg. We complied with the QRH and it led us to believe that we would have degraded braking; no nose wheel steering; and possible no TR's (thrust reversers) upon landing. We called maintenance and confirmed these failures. We decided since [the destination airport] has runways exceeding 12;000 ft; it made the most sense to continue to our destination as the plane was otherwise behaving normally. The PIC briefed the passengers about the issue; assured them of our safe landing; but told them there would be fire trucks. I notified ATC and advised them that we would be needing [the long runway] and it was likely we would have to be towed off the runway. I requested crash fire rescue equipment (crash fire rescue) at the runway; but declined any enroute assistance. We landed without further incident; and were able to taxi to the ramp under our own power.
Original NASA ASRS Text
Title: Bombardier Challenger First Officer reported receiving multiple EICAS messages indicating faults for various systems.
Narrative: I was the PF on [this flight]. While at cruise we started receiving multiple cyan EICAS messages. They read SPOILER FAULT; LT ENGINE FAULT; RT ENGINE FAULT; PROX SYS FAULT; STAB TRIM FAULT. We then got a yellow WOW FAULT yellow caution msg. We complied with the QRH and it led us to believe that we would have degraded braking; no nose wheel steering; and possible no TR's (Thrust Reversers) upon landing. We called maintenance and confirmed these failures. We decided since [the destination airport] has runways exceeding 12;000 ft; it made the most sense to continue to our destination as the plane was otherwise behaving normally. The PIC briefed the passengers about the issue; assured them of our safe landing; but told them there would be fire trucks. I notified ATC and advised them that we would be needing [the long runway] and it was likely we would have to be towed off the runway. I requested CFR (Crash Fire Rescue) at the runway; but declined any enroute assistance. We landed without further incident; and were able to taxi to the ramp under our own power.
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.