ERA19TA211 · Cessna 208 B
ISR Aviation Cessna 208 B · Accident: hard landing
From Blackwater Creek Ultralightport (9FD2) to Blackwater Creek Ultralightport (9FD2)
Event
- NTSB case
- ERA19TA211
- 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 208 B
- Aircraft type
- Cessna 208
- 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
- N80JF
- Operator
- ISR Aviation
- Onboard fatalities
- Unknown
- Route
- From Blackwater Creek Ultralightport (9FD2), Plant City, FLTo Blackwater Creek Ultralightport (9FD2), Plant City, FL
- Aircraft age
- About 26 years (built 1993)
- 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
- Defining eventThe 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was conducting skydiving operations and that the airplane was on final approach to the runway, about 80 ft above ground level and a "few feet before the threshold," when the airplane's windshield became "foggy" and he could not see the runway. He did not attempt to go around because the skydivers were in the area, and he did not want to hit them or trees surrounding the runway. Review of a witness video recording of the landing revealed that the airplane's nose landing gear contacted the runway first, followed by the main landing gear. The airplane bounced, and the nose landing gear impacted the runway again and then collapsed. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The airplane was equipped with a defrost system for the forward cabin windshield. However, the system was likely not being used at the time of the accident.
Probable cause
The pilot's improper landing flare due to reduced visibility from a foggy windshield and his failure to use the airplane’s windshield defrost system, which resulted in a hard landing and subsequent nose landing gear collapse.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA19TA211
- Event ID
- 20190708X35225
- Case number
- ERA19TA211
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 1cb437a302b305eb320ddb3de762713e9e3516f4ca366012d3d96610e94ac4e0; retrieved 2026-09-16T09:23:09.240Z.