MIA05CA097 · Bellanca 8GCBC
Bellanca 8GCBC · Accident: overrun during landing
From 83J · Pensacola, FL to 83J · Pensacola, FL
Event
- NTSB case
- MIA05CA097
- 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
- Unknown
- 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
Bellanca 8GCBC
- Aircraft type
- Bellanca 8
- 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
- N53954
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 83J · Pensacola, FLTo 83J · Pensacola, FL
- 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 · landing roll
- 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
- Overrun
- 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 › Distance/altitude, not performed
- Pilot in command › Go-around, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the NTSB "Pilot/Operator Aircraft Accident Report" form, the aircraft was fast on landing which resulted in a long landing. The pilot applied excessive braking as the end of the runway was approaching causing the aircraft to nose over. A pilot-rated witness on the airport reported the aircraft appeared to make a "...high, overshooting turn to final." The airplane was then observed to be making "S" turns, followed by an "... aggressive side-slip maneuver to lose excess altitude." The aircraft leveled out and "floated" past my position which was located at the midfield point. The airplane touchdown, bounced, and traveled another 200 to 300 feet before touching down again in a two point landing. The aircraft rolled approximately 100 feet before the tail began to rise, and the propeller contacted the ground.
Probable cause
The pilot misjudged his altitude and distance resulting in an overrun. Also causal was the pilot's failure to execute a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA05CA097
- Event ID
- 20050513X00610
- Case number
- MIA05CA097
- 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, coordinates. 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: 0f8583bdfde9a879982bb4dcfaf3b9dc69edd5694537479e312c0d43f9b84c1d; retrieved 2026-09-22T06:00:58.172Z.