FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI99LA030 · Cessna 172C

14 Nov 1998 · Falls City, NE, United States

Cessna 172C · Accident: hard landing

From Sherman Army Air Field (FLV) to Neubrandenburg Trollenhagen Airport (FNB)

Report a problem

Event

NTSB case
CHI99LA030
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 172C

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
N1806Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sherman Army Air Field (FLV), FT. LEAVENWORTH, KSTo Neubrandenburg Trollenhagen Airport (FNB)
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 · flare/touchdown
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
Hard landing
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

  • Flight instructor(on ground) › Inadequate initial training

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

NTSB narrative

On his fourth attempt to land the airplane the student pilot misjudged the flare and hard landed the airplane. The accident flight was the second time the student pilot had operated the airplane solo. The student pilot had accumulated a total flight time of 13.9 hours upon returning to the home field following a hard landing at another airport where he had conducted a round-robin cross country flight. He had received 8.6 hours of dual instruction in preparation for his first solo flight. After that he received an additional 1.8 hours dual instruction in cross country technique. Then his student pilot certificate was endorsed approving solo cross country flights at which point he conducted the accident flight.

Probable cause

the flight instructor (on the ground)'s conducting inadequate initial training of the student pilot. Factors were the student pilot's misjudging the flare and his lack of total experience in the type of operation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI99LA030
Event ID
20001211X11385
Case number
CHI99LA030
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: 29a86b15bc345453a6cf56dfbca9dded1ecc5a2d014c069e5fa6b9e6905b0235; retrieved 2026-09-22T16:20:32.682Z.