WPR18LA259 · Cessna 172 S
Island Air Cessna 172 S · Accident: preflight or dispatch event before flight
From an unrecorded airport to Bellingham International Airport (BLI)
Event
- NTSB case
- WPR18LA259
- 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
Cessna 172 S
- Aircraft type
- Cessna 172
- 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
- N24ME
- Operator
- Island Air
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Bellingham International Airport (BLI), Bellingham, WA
- Aircraft age
- About 18 years (built 2000)
- 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
- Prior to flight
- Defining eventThe 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
- Preflight or dispatch event
- 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
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that he adjusted his seat and “wiggled it” prior to takeoff to ensure it was locked in place. However, during the takeoff roll, the seat moved all the way aft, and the pilot was not able to reach the throttle or the rudder pedals. The airplane veered to the left and lifted off the ground. Shortly after, the tail struck the ground, followed by the left wing, and the airplane came to rest on its nose. A postaccident examination of the seat rail and latching mechanism revealed no anomalies. There was proper hole engagement with the seat pin and holes in the seat rail; the seat did not move once the stop was engaged with the hole. Therefore, it is likely that although the pilot attempted to secure his seat before takeoff, the seat pin was likely not engaged in the corresponding hole in the seat rail, which resulted in its aft movement when the airplane gained speed during the takeoff roll.
Probable cause
The pilot’s failure to secure his seat position prior to takeoff, which resulted in a loss of airplane control and subsequent hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18LA259
- Event ID
- 20180912X30613
- Case number
- WPR18LA259
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 159e8056dd4292cb2e76b52066c449e682185cb579aabf90a22886e533e040be; retrieved 2026-09-16T08:14:23.402Z.