MKC83LA174 · Cessna 152
Cessna 152 · Accident: loss of engine power en route
From Brighton Van-Aire Estates Airport (CO12) to an unrecorded destination
Event
- NTSB case
- MKC83LA174
- 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
Cessna 152
- Aircraft type
- Cessna 152
- 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
- N67585
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Brighton Van-Aire Estates Airport (CO12), Brighton, COTo not recorded
- Aircraft age
- Not recorded
- 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
- En route · descent
- First occurrenceThe 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 engine power
- 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
- Pilot in command › Diverted attention
- Pilot in command › Emergency procedure, improper
- Pilot in command › Flare, improper
- Pilot in command › Powerplant controls, improper use of
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PLT WAS ON A SOLO X-COUNTRY FLT. AS HE APPROACHED SIDNEY, NE, HE WAS UNABLE TO CONTACT ANYONE ON THE RADIO & CONTINUED TO THE ARPT AT CRUISE ALT. HE DESCENDED WHILE CIRCLING THE ARPT. BEFORE REACHING TRAFFIC PATTERN ALT, HE APPLIED POWER, BUT THE ENG DID NOT RESPOND. THE STUDENT DECLARED AN EMERGENCY & TURNED TOWARD THE ARPT. HE WAS UNABLE TO LOSE BOTH AIRSPEED & ALT. WHEN HE FORCED THE ACFT ON THE RWY, IT BOUNCED SEVERAL TIMES, THEN HIT, NOSE & LEFT WING LOW & WAS SUBSTANTIALLY DAMAGED. ACCORDING TO STUDENT'S INSTRUCTOR, THE STUDENT HAD FORGOTTEN TO ENRICH THE MIXTURE AFTER DESCENDING, THEN PANICKED WHEN HE THOUGHT THE ENG FAILED. THE TEMP & DEW POINT WERE 81 & 57 DEG, RESPECTIVELY. ACCORDING TO THE ICING PROBABILITY CHARTS, SERIOUS CARBURETOR ICE COULD OCCUR IN FLOAT CARBURETORS AT GLIDE POWER. THE USE OF CARBURETOR HEAT WAS NOT VERIFIED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MKC83LA174
- Event ID
- 20001214X44274
- Case number
- MKC83LA174
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: b34303d00546e3902d789366960c9e2071cfed54f5b3be7091857f7f2d8d19f4; retrieved 2026-09-23T21:39:34.467Z.