19900310003649I

Incident

FAA incident report · Boeing 737-301 · Baltimore, MD · March 10, 1990

Date: March 10, 1990 · 21:22 local
Place: Baltimore, MD
Airport: Baltimore-Washington International
Phase of flight: Normal Cruise
Operating rules: Air carrier (Part 121)
Operator: USAA
Aircraft: N355US
Reported as: Boeing 737301
People aboard: 2
Fatal injuries: 0

N355USRegistration cancelled Aug 9, 2006 · Boeing 737-301S/N 23558 · Built 1987 Airframe modelBoeing 737-301 Engine modelCFM International CFM56 seriesTurbo-fan

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Partial electrical failure en route. Relay failure. On landing air cycle machine overheated and smoked. Evacuted.

As the FAA filed it

PARTIAL ELECTRICAL FAILURE EN ROUTE. RELAY FAILURE. ON LANDING AIR CYCLE MACHINE OVERHEATED AND SMOKED. EVACUTED.

Other reports on N355US · 2

Matched to the same aircraft by N-number and date.

Incident 20020323009979ITakeoff Ground Roll · Kansas City, MO(-23) On March 23, 2002 us airways flight 386 a B737 aborted takeoff due to an APU caution light. Aircraft returned to the terminal. Log entry indicated at takeoff roll the APU det. In-op light illuminated, takeoff rejected. The APU fire detection system was…Mar 23, 2002 Incident 19900311013479INormal Cruise · Baltimore, MDElectrical failure due to relay failure. On landing air cycle machine overheated and smoked. Evacuated aircraft.Mar 11, 1990