FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MKC83LA077 · Cessna 172

15 Mar 1983 · Greenfield, MO, United States

Cessna 172 · Accident: in flight collision with object during landing

From Springfield Branson National Airport (SGF) to an unrecorded destination

Report a problem

Event

NTSB case
MKC83LA077
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 172

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
N6258E
Onboard fatalities
Unknown
Route
From Springfield Branson National Airport (SGF), Springfield, MOTo 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
Landing
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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire, transmission
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 › Go-around, delayed

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

NTSB narrative

THE PLT REPORTED THAT BEFORE LANDING HE APPLIED CARBURETOR HEAT & EXTENDED FULL FLAPS. REPORTEDLY, HE MADE A STEEP APPROACH TO THE 3000 FT, SOD RWY. HE SAID HE OVERSHOT THE 1ST HALF OF THE RWY & TOUCHED DOWN AT ABOUT MIDFIELD. AT THIS POINT, THE PLT INITIATED A GO-AROUND. INITIALLY, HE APPLIED FULL THROTTLE, REMOVED THE CARBURETOR HEAT & REDUCED THE FLAPS TO 30 DEG. THE PLT STATED THE ACFT ACCELERATED SLOWLY & SETTLED BACK ONTO THE RWY WHEN THE FLAPS WERE REDUCED TO 20, THEN 10 DEG. THE ACFT PASSED THE END OF THE RWY WITH 10 DEG OF FLAPS. THE PLT WAS ABLE TO PULL UP & CLEAR TREES & A POWER LINE. AFTER CROSSING, THE OBSTACLES, HE LOWERED THE NOSE, THEN TURNED TO AVOID A HOUSE. HOWEVER, THE ACFT WOULD NOT CLIMB OVER THE RISING TERRAIN. THEREFORE, THE PLT ELECTED TO LAND IN A PASTURE, BUT THE ACFT HIT A LOW VOLTAGE LINE, THEN AFTER LANDING, IT HIT A STUMP & NOSED OVER. THE OWNER'S MANUAL RECOMMENDED ZERO FLAPS FOR TAKEOFFS OVER OBSTACLES.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MKC83LA077
Event ID
20001214X42544
Case number
MKC83LA077
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1983-03-16.
  • API snapshot SHA-256: 2371f2722453ae9a5573643d7240078da26c04e91657e53d669ffde3313d991a; retrieved 2026-09-23T22:47:26.445Z.