WPR19TA034 · Cessna 172 M
Kingdom, Power, and Glory Cessna 172 M · Accident: runway excursion during takeoff
From City of Colorado Springs Municipal Airport (COS) to City of Colorado Springs Municipal Airport (COS)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR19TA034
- 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 M
- 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
- N27LA
- Operator
- Kingdom, Power, and Glory
- Onboard fatalities
- Unknown
- Route
- From City of Colorado Springs Municipal Airport (COS), Colorado Springs, COTo City of Colorado Springs Municipal Airport (COS), Colorado Springs, CO
- Aircraft age
- About 43 years (built 1975)
- 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 › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Action/decision
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, during a touch-and-go landing, he applied full power to take off and, although the airplane departed the runway surface about 50 knots, it did not accelerate, and the airspeed decreased. The airplane began exhibiting characteristics consistent with a stall and he lowered the nose. The airplane then settled back onto the ground slightly off the left side of the runway surface and continued through a grassy field, a fence, and a ditch. The airplane nosed over and came to rest inverted, resulting in substantial damage. Witnesses reported observing the airplane in a nose-high attitude before it descended from view. The flaps were found extended to 40° at the accident site. The density altitude at the time of the accident was about 7,386 ft, and there was an approximate 4-knot tailwind for the landing runway, which had a 1.4% upslope. According to the Federal Aviation Administration Airport/Facility directory, the opposite runway was recommended for touch-and-go landings in tailwind conditions up to 5 knots. According to the manufacturer's takeoff performance chart, there was adequate runway available for takeoff; however, given the high-density altitude, the tailwind, and the runway upslope, the distance required to conduct a touch-and-go landing and takeoff distance were significantly increased, which resulted in the airplane’s inability to become airborne within the remaining runway.
Probable cause
The pilot's decision to perform a touch-and-go landing at a high-density altitude airport, with a tailwind, and on an upsloping runway, which resulted in decreased airplane performance and the airplane’s inability to become airborne within the available runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19TA034
- Event ID
- 20181130X82212
- Case number
- WPR19TA034
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
- 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: d96caf01f3d7a4c948713cc6fb7a548ad38fc2f5557553ee1b2d511d8f7e7ce8; retrieved 2026-09-16T08:28:14.084Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: departure, destination. COS is Colorado Springs Municipal Airport at Colorado Springs, CO; the city name is missing its final s. COS is Colorado Springs Municipal Airport at Colorado Springs, CO; the city name is missing its final s.