Alaska Airlines Flight 500
Boeing 737-400 · Incident: airframe, component or system failure en route
From Portland International Airport (KPDX) to KSFF · San Francisco, CA
Event
- NTSB case
- SEA00IA019
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Unknown
Boeing 737-400
- Aircraft type
- Boeing 737
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N772AS
- Operator
- Alaska Airlines
- Onboard fatalities
- Unknown
- Route
- From Portland International Airport (KPDX)To KSFF · San Francisco, CA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · climb to cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Electrical system, electric wiring › Arcing
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight returned to its departure point after encountering apparent electrical problems, including circuit breakers open for the center tank right pump and the right tank forward pump. After landing, the crew performed a normal shutdown. During taxi in, they noted an electrical smell, which they originally attributed to use of the galley ovens. When they elected to disembark the passengers, passengers leaving the airplane who had been seated mid-cabin noted that they had smelled electrical smoke. The airplane was repowered by maintenance personnel after shut-down and disembarking of passengers. During the trouble-shooting process, additional systems and indicators were affected, including right wing anti-ice and right wing overheat. Technicians isolated an electrical short to the forward cargo compartment. When they touched the panel around station 410, they saw some sparks. Power was removed from the aircraft once the damage was found. The technicians opened the ceiling panel to gain access to the area. When they touched the bottom of the raceway clamp, it fell apart. FAA and NTSB investigators documented the damaged wiring bundles at station 420 above the forward cargo compartment ceiling on the right side of the airplane, and had them sectioned for further inspection and testing. The wire bundle channel and clamp were also removed for inspection and analysis. A total of 113 conductors were reported to have been subjected to the electrical arcing event. Investigators were unable to determine the cause of electrical arcing that burned numerous wires of the subject bundles in two. One of the nine Teflon insulated wires, W336-003-10, exhibited evidence that it might have been damaged prior to the electrical arcing. W336-003-10, and two other 10 gauge wires in the bundles, were conductors for the three-phase 115VAC system A electric hydraulic pump. Electrical arcing had damaged approximately twelve inches of insulation on wire W336-003-10. The exposed conductors at one end of the wire had sustained arc damage at two locations. The arcing burned several wire strands in two, which became unraveled from the rest of the strands. There was approximately one third of the insulation left in this area of the wire. A small area of the edge of the insulation appeared to have been cut prior to the occurrence of the electrical arcing. The wire bundle channel (bracket) and clamp were also analyzed. Evidence indicated that an unidentified wire that was involved in the arcing/burning event had been out of place, along the side of the bracket between the cushioning foam and the plastic (nylon) frame before or during the event. Analysis of these two parts could not determine what type of wire had caused the damage to the side of the cushion clamp or the nylon channel.
Probable cause
Arcing in the electrical system wiring for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA00IA019
- Event ID
- 20001212X20175
- Case number
- SEA00IA019
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: bb5d919c84a4e0fc06d7e3136d251c98935744567bf2fbd3b57eb76ec230cde6; retrieved 2026-09-18T16:51:25.778Z.