SEA92LA211 · Beech A36
P.J. Taggares Beech A36 · Accident: overrun during takeoff
From S08 to Ochoa Field (6WA4)
Event
- NTSB case
- SEA92LA211
- 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
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N144PT
- Operator
- P.J. Taggares
- Onboard fatalities
- Unknown
- Route
- From S08To Ochoa Field (6WA4), Othello, WA
- 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
- Takeoff · roll/run
- 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
- Overrun
- 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 › Removal of control/gust lock(s), not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AT THE BEGINNING OF THE FLIGHT, DURING THE TAKEOFF GROUND RUN, THE PILOT REALIZED THAT HE HAD NOT REMOVED THE AIRPLANE'S CONTROL GUST LOCK. THE PILOT WAS UNABLE TO STOP THE AIRPLANE BEFORE IT TRAVELLED OFF THE END OF THE RUNWAY, COLLIDED WITH A FENCE AND CAME TO REST PARTIALLY SUBMERGED IN THE BAY NORTH OF THE AIRSTRIP. THE PILOT REPORTED THAT THE AIRPLANE WAS NORMALLY KEPT IN A HANGAR AND THAT THE GUST LOCK WAS NOT USED. THE DAY BEFORE THE ACCIDENT, ANOTHER PILOT HAD FLOWN THE AIRPLANE AND LEFT IT OUTSIDE THE HANGAR, AND HAD INSTALLED THE GUST LOCK. THE LOCK THAT WAS USED WAS JUST THE PIN, AS THE RED CAUTION FLAG HAD PREVIOUSLY BROKEN OFF. THE PILOT DID NOT SEE THAT THE PIN WAS INSTALLED DURING THE PREFLIGHT INSPECTION. THE PILOT ALSO REPORTED THAT HE DID NOT USE A CHECKLIST AND AT NO TIME DURING THE PREFLIGHT INSPECTION DID HE CHECK FOR FREEDOM OF MOVEMENT OF THE FLIGHT CONTROLS.
Probable cause
THE REMOVAL OF THE CONTROL GUST LOCK WAS NOT PERFORMED. FACTORS TO THE ACCIDENT WERE: INADEQUATE PREFLIGHT, THE CHECKLIST WAS NOT USED, AND THE CONTROL GUST LOCK MARKING FLAG WAS GONE DUE TO PREVIOUS DAMAGE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA92LA211
- Event ID
- 20001211X15783
- Case number
- SEA92LA211
- 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: ce779454742cc245a20bcf621b40bb718df99c99b8a647dc63a73ebe798d0eda; retrieved 2026-09-21T23:07:19.025Z.