CHI01LA050 · Beech 58
Beech 58 · Accident: in flight collision with terrain/water on approach
From Page Field (FMY) to Huntingburg Airport (HNB)
Event
- NTSB case
- CHI01LA050
- 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
- Instrument 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
- N4558S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Page Field (FMY), FORT MEYERS, FLTo Huntingburg Airport (HNB)
- 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
- Approach · IFR final approach
- 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
- In flight collision with terrain/water
- 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 › Proper touchdown point, not obtained/maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane landed 15 feet short of runway 09 following a go-around from an instrument approach. The pilot initiated a go-around when a snowplow entered the runway. The pilot reported that he made two position reports on the UNICOM frequency. The first report was 30 miles or 15 minutes from the airport and the second was 1 to 1-1/2 miles during the final approach. The driver of the snowplow reported only hearing the 15-minute call and heard a second transmission while the airplane was flying over him. The pilot stated that the airplane 'mushed' when power was reduced in an attempt to land on the 'numbers'. The pilot had the trailing edge flaps retracted. The pilot also stated that the windshield deice was working while en route but was not functioning during the approach. Approximately 1/2 of the windshield was contaminated by ice. A notice to airman indicated that braking action was poor with 0.25 inches of snow.
Probable cause
The proper touchdown point not obtained/maintained by the pilot. Factors were the snow covered runway, the ice contaminated windshield, and the airport snow removal performed by the driver of the vehicle.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01LA050
- Event ID
- 20001229X45499
- Case number
- CHI01LA050
- 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: 9a4f6019be9eb160babecc5e3fe6bf95ecf5922302f11f720054f0913c4293d0; retrieved 2026-09-22T12:16:35.750Z.