- Date
- March 18, 1972
- Place
- Edgerton, KS · EDGERTON, KS
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N3679CCessna 180
- Status
- Completed · report November 1, 1972
- Report
- Brief approved by the director
- Case key
- 165795
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-0568 72/3/18 EDGERTON,KANS CESSNA 180 CR- 0 0 1 MISCELLANEOUS COMMERCIAL, FL.INSTR., TIME - 1330 N3679C PX- 0 0 0 PARAJUMP-SPORT AGE 38, 318 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 9 IN TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - KONITZ DEPARTURE POINT INTENDED DESTINATION EDGERTON,KANS LOCAL TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: DESCENDING HARD LANDING LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION PILOT IN COMMAND - MISJUDGED DISTANCE,SPEED,AND ALTITUDE PILOT IN COMMAND - IMPROPER LEVEL OFF FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - POORLY PLANNED APPROACH MISCELLANEOUS ACTS,CONDITIONS - NOT ALIGNED WITH RUNWAY/INTENDED LANDING AREA COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT. REMARKS- ENG CUT OUT IN LETDOWN AND PATTERN.PSN TOO CLOSE IN,HAD TO APCH OTR RWY.DIDNT LINE UP PROPERLY.
Aircraft
- Registration
- N3679C
- Reported as
- Cessna 180
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Konitz
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.