ERA10CA191 · Beech 58
Beech 58 · Accident: hard landing
From Melbourne Orlando International Airport (MLB) to Naples Municipal Airport (APF)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA10CA191
- 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
Beech 58
- Aircraft type
- Beechcraft 58
- 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
- N858PR
- Operator
- Golpa Gadoda
- Onboard fatalities
- Unknown
- Route
- From Melbourne Orlando International Airport (MLB), Melbourne, FLTo Naples Municipal Airport (APF), Naples, 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 · 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
Upon arrival at his destination after an instrument-flight-rules flight, the pilot was cleared for a very-high frequency omnidirectional radio range approach to runway 5. The pilot encountered visual conditions at 400 feet. He flared the airplane high and fast and the airplane touched down hard on the runway and bounced. The airplane touched back down on the runway and began to porpoise. The nosewheel then sheared off and the airplane continued down the runway until it came to a complete stop. Both wings were wrinkled to their wing root and the cabin area was buckled. The pilot stated that there was nothing mechanically wrong with the airplane and that he simply "rounded out" too high and made a hard landing, resulting in the nose landing gear shearing off the airplane.
Probable cause
The pilot's improper flare while landing, resulting in a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA191
- Event ID
- 20100329X70850
- Case number
- ERA10CA191
- 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: ce5942b73cbbb7ffc569c487e713346e2ade4adc13e80bc2971bdc31a24e216d; retrieved 2026-09-15T13:48:07.590Z.