SEA06LA109 · Piper PA-28-160
Piper PA-28-160 · Accident: loss of control in flight while maneuvering
From Laurel Municipal Airport (6S8) to Billings Logan International Airport (BIL)
Event
- NTSB case
- SEA06LA109
- 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
Piper PA-28-160
- Aircraft type
- Piper PA-28
- 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
- N1123W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Laurel Municipal Airport (6S8), Laurel, MTTo Billings Logan International Airport (BIL), Billings, MT
- 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
- Maneuvering · turn to reverse direction
- 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 in flight
- 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
- Company maintenance personnel › Maintenance, installation, improper
- Other maintenance personnel › Maintenance, installation, not verified
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the recent annual inspection the left-hand control yoke had been removed from the left-hand control column in compliance with a current FAA airworthiness directive; the control yoke was subsequently reinstalled to its respective control column. After taking off and beginning a left turn, the pilot experienced no aileron control input, impacting terrain in a nose low attitude. A post-accident examination revealed that the left-hand control yoke had not been properly reinstalled or verified that that installation was correct.
Probable cause
The failure of maintenance personnel to properly reinstall the left-hand control yoke to the left-hand control column, and the failure of other maintenance personnel to properly verify the installation, which resulted in the pilot's loss of control in flight while maneuvering and subsequent impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06LA109
- Event ID
- 20060616X00752
- Case number
- SEA06LA109
- 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: efcd9d49a4216f6f8be90de03810298a5012222807ffb831016226f8d28210de; retrieved 2026-09-21T08:57:30.569Z.