MIA99LA101 · Cessna 177
Cessna 177 · Accident: hard landing
Event
- NTSB case
- MIA99LA101
- 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 177
- Aircraft type
- Cessna 177
- 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
- N2890X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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 · 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
- Pilot in command › Flare, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was practicing landings on runway 15, and was on his fourth takeoff. He said, '...on the downwind I went to push the control forward and it would not go.' He attempt an approach to runway 15, but on final he was too high and decided to go around and try another approach. The pilot said, '...I was on final I was at 400 [feet] agl, and cut the power back to idle and hit the runway about 100 mph. The plane went end to end several times and hit the runway several times...I ended up on the east side of the grass.' The pilot taxied the airplane to the parking area and noted that the airplane was damaged. Examination of the wreckage revealed a stop drilled crack in the tail cone fairing assembly adjacent to the elevator that appeared to interfere with the travel of the flight control surface. Further examination revealed that the tail cone had sustained impact damage in the area of the stop drill crack. According to the FAA inspector the impact damage caused the interference with the travel of the flight control, and that the crush occurred after the pilot had made a hard landing, causing the damage.
Probable cause
the pilot misjudged the flare, resulting in a hard landing, and subsequent impact with the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA101
- Event ID
- 20001205X00363
- Case number
- MIA99LA101
- 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: deb29a5499728555c789f6ad43338f4b87d54277a637d7e3483ed24be526b8fc; retrieved 2026-09-22T15:45:06.999Z.