FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN83LA057 · Cessna 182Q

11 Feb 1983 · Burlington, CO, United States

Associates Flying Club Cessna 182Q · Accident: loss of control on ground/water on approach

From Centennial Airport (APA) to an unrecorded destination

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
DEN83LA057
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 182Q

Aircraft type
Cessna 182
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
N94618
Onboard fatalities
Unknown
Route
From Centennial Airport (APA), Englewood, 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
Approach · VFR go-around
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 control on ground/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Airspeed, above
  • Pilot in command › Compensation for wind conditions, improper
  • Pilot in command › Distance, misjudged
  • Pilot in command › Go-around, delayed
  • Pilot in command › Ground loop/swerve, not corrected
  • Pilot in command › Lowering of flaps, improper use of
  • Pilot in command › Wrong runway, selected

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE ACFT CRASHED DURING AN ATTEMPTED GO-AROUND. THE PILOT HAD LANDED DOWNWIND WITH AN APPROACH SPEED OF 80 KTS AND 25 DEGREES FLAPS. THE PILOT SAID HE USED RWY 13 INSTEAD OF 31 BECAUSE OF A NOTAM PROHIBITING LANDING ON RWY 31. THERE WAS NO NOTAM TO THAT EFFECT NOR WAS THERE A NOTAM PROHIBITING TAKEOFFS ON RWY 13. DURING LANDING ROLL THE PILOT REALIZED HE WAS TOO FAR DOWN THE RWY AND GOING TOO FAST. HE STARTED A GO-AROUND. A WITNESS SAW THE ACFT 1000 FT FROM THE DEPARTURE END OF THE RWY & MOVING AT A HIGH RATE OF SPEED. HE SAID THE ACFT WENT OFF THE RIGHT SIDE OF THE RUNWAY ABOUT 300-400 FROM THE END OF RWY 13. THE ACFT'S NOSE GEAR WAS OFF THE GROUND BUT THE MAIN GEAR WAS NOT. 'THE PILOT THEN PUSHED THE THROTTLE IN AS IF TO MAKE A GO-AROUND'. HE ALSO STATED THE ACFT WENT THROUGH A FENCE, HIT A RAILROAD TRACK AND FLIPPED IT OVER.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record DEN83LA057
Event ID
20001214X42180
Case number
DEN83LA057
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: 96fac167b12b6d6d4bff5c237fe7c3ed1d37daf5f244a6a1672e666c6d8085b7; retrieved 2026-09-22T02:46:56.260Z.