FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA07LA213 · Boeing A-75

21 Jul 2007 · Spokane, WA, United States

Boeing A-75 · Accident: airframe, component or system failure during landing

From Felts Field (KSFF) to Felts Field (KSFF)

Report a problem

Event

NTSB case
SEA07LA213
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
Accident
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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Boeing A-75

Aircraft type
Boeing A-75
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
N56551
Operator
Unknown
Onboard fatalities
Unknown
Route
From Felts Field (KSFF), Spokane, WATo Felts Field (KSFF)
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 91: General Aviation
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
Landing · landing roll
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
Substantial

Cause areas

  • Landing gear, normal brake system › Locked

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Soon after touching down on the main landing gear, the airplane's left brake locked up, and the airplane began to veer toward the edge of the runway. During the pilot's attempts to keep the airplane rolling straight, both bottom wings came in contact with the runway surface, and the airplane nosed over. The airplane's left tire had created a significant skid mark starting just past where the airplane touched down. There was no evidence of skidding of the right main landing gear tire. The investigation did not reveal any reason for the malfunction of the left brake, but the skid mark on the runway indicated that the brake mechanism had malfunctioned or locked up while the airplane was in the air, or during the touchdown sequence.

Probable cause

The locking/seizing of a main landing gear brake mechanism during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA07LA213
Event ID
20070808X01150
Case number
SEA07LA213
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, coordinates. 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: 531930d8ab2e579e6f6006a7a1cc8d042845149216c9775d18c5f5554cb2f652; retrieved 2026-09-22T03:37:57.528Z.