American Airlines Flight 268
Boeing 757-223 · Incident: electrical system malfunction/failure en route
From Seattle–Tacoma International Airport (SEA) to John F. Kennedy International Airport (JFK)
Event
- NTSB case
- CHI08IA292
- 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
- Unknown
- 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
- Not recorded
Boeing 757-223
- Aircraft type
- Boeing 757
- 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
- N197AN
- Operator
- American Airlines
- Onboard fatalities
- Unknown
- Route
- From Seattle–Tacoma International Airport (SEA), Seattle, WATo John F. Kennedy International Airport (JFK), New York, NY
- 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
- Defining eventThe 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
- Electrical system malfunction/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
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While performing the cockpit preflight, the captain noticed that the standby horizon was unpowered. After cycling the Standby Power Selector and the Battery Switch, the captain noted that five status messages were displayed on the engine indicating and crew alert system (EICAS) screen, although he could not remember the specific messages. Maintenance personnel subsequently cleared the messages and told the crew they were "good to go," without making a logbook entry. Approximately 30 minutes after takeoff several cockpit lights flickered; multiple EICAS messages appeared, including the AIR/GRD SYS caution message; the Standby Power OFF light illuminated; the autopilot disconnect warning sounded; and the autothrottles disconnected. The first officer referenced the STANDBY BUS OFF procedure in the QRH, turning the Standby Power selector to the BAT position. The QRH states that when BAT is selected the battery will provide bus power for approximately 30 minutes. Although the QRH did not instruct the crew to divert to the nearest suitable airport, it indicates that the battery will supply bus power for approximately 30 minutes and the captain reported to maintenance that the battery would be depleted. After consulting with company maintenance specialists, the crew elected to continue the flight. Battery power was depleted and numerous essential aircraft systems began to fail about 2 hours and 24 minutes after the flight crew switched the Standby Power selector to the BAT position. These systems included the stabilizer trim, the captain’s instrumentation, thrust reversers, anti-skid and others. The flight diverted to the closest airport, an emergency was declared, and the airplane was cleared to land on the 7,500-foot-long runway; the captain stated that due to problems controlling the airplane, he did not want to circle to land on a longer runway. The airplane touched down hard about 2,500 feet down the runway. The crew determined they were going to overrun the end of the runway, so the captain veered the airplane off the left side of the runway into the grass, where the airplane came to rest with seven of the eight main gear tires either blown out or deflated. Postaccident investigation revealed erosion on the B contacts within the K106 relay; a failure of the K106 electrical relay would result in the events described by the crew.
Probable cause
The failure of an electrical relay due to eroded contacts and the flight crew's decision to continue a flight that was operating on battery power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08IA292
- Event ID
- 20081007X03940
- Case number
- CHI08IA292
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: a47bc097481e96e54fe351c2c971a9fe29e663be249aaef8d39c2443270435eb; retrieved 2026-09-15T10:24:50.862Z.