SEA00LA195 · Boeing E75
Boeing E75 · Accident: loss of control on ground/water while taxiing
From Salem-Willamette Valley Airport/McNary Field (SLE) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- SEA00LA195
- 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
- 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
- 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 E75 Possible conflict
- Aircraft type
- Boeing E75
- 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
- N8528N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Salem-Willamette Valley Airport/McNary Field (SLE)To not recorded
- 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
- Taxi · to runway
- 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
- Loss of control on ground/water
- 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
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that 45 minutes before the accident, he had washed the aircraft's engine with water and engine cleaner and that he intended to dry the engine by flying once around the local traffic pattern. The pilot stated that 'as [the] taxi progressed [the] brakes became progressively non functional and [the] aircraft began a slow turn to the left aided by a strong tailwind.' The pilot reported that attempts to stop the aircraft and to maintain directional control by braking were ineffective 'in spite of VERY strong pedal pressure' (emphasis in original). The pilot stated that power was at idle when the continuing turn ended in a collision with a parked and unoccupied Cessna airplane at about 4 MPH. The pilot stated that the aircraft's brakes became wet during taxi.
Probable cause
The pilot's failure to maintain aircraft control upon experiencing a loss of normal braking effectiveness. Factors included a partial failure of the brake system, a tailwind, and a parked aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA00LA195
- Event ID
- 20001212X22088
- Case number
- SEA00LA195
- 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: c7eae1be0aa5ac2856b5736c65d4f3b01937c9226fb51af074f3e2c00d13bde2; retrieved 2026-09-22T12:24:33.966Z.