FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA104 · Textron Aviation Inc 172S

31 Jan 2026 · Augusta, KS, United States

Textron Aviation Employees Flying Club Textron Aviation Inc 172S · Accident: loss of control on ground during takeoff

Report a problem

Event

NTSB case
CEN26LA104
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

Textron Aviation Inc 172S

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
N767VK
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 3 years (built 2023)
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
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
Loss of control on ground
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 student pilot planned to perform three takeoffs and landings, and one go-around for her solo flight. After completing the third landing, the student pilot stated that she still needed to perform a go-around and decided to take off for a fourth time. After she applied takeoff power, the airplane began to drift toward the left edge of the runway. To avoid going into the snow, she rotated and “tried to make it fly.” The airplane became partially airborne before it touched back down. The pilot then applied the brakes and the airplane nosed over and came to rest inverted in the snow next to the runway. The airplane sustained substantial damage to the aft fuselage and vertical stabilizer. The student pilot reported that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation.

Probable cause

The student pilot’s failure to maintain control during the takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN26LA104
Event ID
20260202202373
Case number
CEN26LA104
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, 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: db89ec420d6ca7efc442bedd370d92c196dbdce33d1083792504ca77c171ce97; retrieved 2026-09-16T20:42:40.017Z.