WPR19CA072 · Cessna R172 K
Axiom Aviation Cessna R172 K · Accident: runway excursion during takeoff
From Ogden, UT to Ogden, UT
Event
- NTSB case
- WPR19CA072
- 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 R172 K
- 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
- N736TB
- Operator
- Axiom Aviation
- Onboard fatalities
- Unknown
- Route
- From Ogden, UTTo Ogden, UT
- Aircraft age
- About 42 years (built 1977)
- 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
- Runway excursion
- 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
- Environmental issues › Physical environment
- 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 student pilot and flight instructor reported that, after conducting maneuvers, they proceeded to the airport to practice touch-and-go takeoffs and landings. The student landed the airplane off the runway centerline and then raised the flaps and added power. The airplane continued forward and impacted snow along the edge of the runway, nosed over, and then came to rest inverted. The airplane sustained substantial damage to the right wing and vertical stabilizer. The instructor and student reported that there were no preaccident mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation.
Probable cause
The student pilot's failure to maintain the runway heading during a touch-and-go landing and the flight instructor's delayed remedial action, which resulted in the airplane departing the left side of the runway, impacting snow, and nosing over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19CA072
- Event ID
- 20190125X53851
- Case number
- WPR19CA072
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2019-01-24.
- API snapshot SHA-256: fd46ad03fd2069e7a1cab8b90165cb3e01d05b6b582694174ac894cee3a1b8f2; retrieved 2026-09-16T08:33:35.213Z.