SEA99LA064 · Boeing B75N1
Boeing B75N1 · Accident: loss of control on ground/water during landing
From Olympia Regional Airport (OLM) to Chehalis Centralia Airport (CLS)
Event
- NTSB case
- SEA99LA064
- 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 B75N1
- Aircraft type
- Boeing B75
- 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
- N275HP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Olympia Regional Airport (OLM), Olympia, WATo Chehalis Centralia Airport (CLS)
- 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
- 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 › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the landing was made with a slight crosswind from the left. The pilot stated that during the landing roll, the right brake locked during normal corrective braking for directional control and stopping. The airplane swerved to the right and the pilot was unable to correct with left rudder control and left braking action. The airplane subsequently ground looped to the right. After the accident, a 50-foot long arcing skid mark was noted on the runway. The pilot stated that he thought that moisture might have caused the brake malfunction, as the airplane had not been flown for several months. The pilot also stated that he could not duplicate the 'locked brake' during subsequent taxiing. A mechanic inspected the brake after the accident and reported no evidence was found to indicate a mechanical failure or malfunction. In a later written statement, he noted that drum type brakes such as those that were on the Stearman are notorious for grabbing due to moisture. The pilot had disc brakes installed on the airplane after it was repaired following the accident. A mechanic had noted no visual mechanical discrepancies of the wheel or brake when he looked at them a few weeks after the accident. When the airplane was reassembled after repair, the right wheel was jacked up and the wheel was spun and the brake applied for proper action.
Probable cause
Directional control was not maintained after the right brake locked up for undetermined reasons. An uncontrolled ground loop was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA99LA064
- Event ID
- 20001205X00570
- Case number
- SEA99LA064
- 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: 2616afd200988cff43e5ece877f110221f987e9914cdd2bb7d8310f6386e8f2d; retrieved 2026-09-22T15:22:55.211Z.