CEN16LA089 · Cessna 208B
Sartec Cessna 208B · Accident: aircraft loading event while standing
From Anoka County-Blaine (Janes Field) Airport (KANE) to Grand Forks International Airport (KGFK)
Event
- NTSB case
- CEN16LA089
- 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
- Instrument Meteorological Cond
Cessna 208B
- Aircraft type
- Cessna 208
- 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
- N617ST
- Operator
- Sartec
- Onboard fatalities
- Unknown
- Route
- From Anoka County-Blaine (Janes Field) Airport (KANE), Anoka, MNTo Grand Forks International Airport (KGFK), Grand Forks, ND
- Aircraft age
- About 11 years (built 2004)
- 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
- Standing · engine(s) not operating
- 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
- Aircraft loading 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 › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot was conducting a cross-country business flight. He landed the airplane and then taxied to the ramp. The pilot instructed the passengers to remain seated and then deplaned to attach the tailstand, at which point the airplane tipped back and struck the pavement with its tail. The pilot reboarded and instructed the passengers to leave their seats and move forward, and the airplane righted itself. The forward bulkhead for the horizontal stabilizer attachment point was crushed and torn, and three stringers, another bulkhead, and the lower skin were damaged in the accident. The center of gravity (CG) was calculated postaccident based on the available weight and balance data, and it was aft of the CG limit. It is likely that the pilot did not properly calculate the airplane's weight and balance and CG, which resulted in the airplane tipping backward as the pilot attempted to attach the tailstand.
Probable cause
The pilot's failure to properly calculate the airplane's weight and balance and center of gravity, which resulted in the tail striking the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA089
- Event ID
- 20160119X45136
- Case number
- CEN16LA089
- 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. 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: 092eb5a07fe9c95301b3dfc7e91c3252279d97658b9a254ed11baadf431f0f54; retrieved 2026-09-16T03:05:53.143Z.