MIA05LA049 · Beech B300
Cbi Beech B300 · Accident: overrun during landing
From Witham Field (KSUA) to Jacksonville Executive at Craig Airport (KCRG)
Event
- NTSB case
- MIA05LA049
- 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
- Instrument Meteorological Cond
Beech B300
- Aircraft type
- Beechcraft 300
- 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
- N350CS
- Operator
- Cbi
- Onboard fatalities
- Unknown
- Route
- From Witham Field (KSUA), Stuart, FLTo Jacksonville Executive at Craig Airport (KCRG), Jacksonville, 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
- 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 › Missed approach, 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
The pilot obtained three preflight weather briefings for the accident flight. The first weather briefing was the evening before the flight, while the last two were obtained the morning of the accident flight. The accident flight departed and ATIS information was obtained when the flight was approximately 30 miles from the destination airport. The ATIS at that time indicated scattered clouds existed at 100 feet with 2 miles visibility. The flight continued and after passing the final approach fix during the ILS approach to runway 32, the tower controller advised the flight crew of an indefinite ceiling of 100 feet with 3/4 mile visibility, with the visibility being supplemented by the ground controller who is a National Weather Service train weather observer, from the previous weather observation taken at 0807. The audible alarm for the ASOS monitor was on at the time of the accident. The ASOS monitor was located due east from the center of the tower cab near the ground control position, while the local control position was located north-northwest from the center of the tower cab. At 0826, a special METAR weather observation was taken indicating the visibility was 1/4 statute mile with fog, and a vertical visibility was 100 feet; the special observation was not provided to the flight crew. At the time the special METAR was taken, the airplane was inside the final approach fix and at an altitude less than 459 feet above ground level. The pilot advised he was flying the airplane at Vref plus 4 knots, and both he and copilot reported the runway environment became visible when the flight was approximately 200 feet agl. During the flare for landing, the flight entered heavy fog. The pilot further reported that he could not determine the point of touchdown; however, while on the ground, the airplane passed the 1000 foot-remaining marker. Full braking and reverse was applied; however, the airplane traveled off the end of the runway onto wet grass and collided with a localizer antenna 557 feet past the departure end of the runway. The pilot further reported there was no preimpact failure or malfunction of the aircraft, aircraft systems, or engines. He also reported that the reason for the overrun was not due to the additional 4 knots, but was due to the fact that while flaring to land with the engines spool down, full flaps extended, and the indicated airspeed below Vmc, fog rolled over the runway severely limiting my view of it. As a result he had to "... feel for the runway" which extended the touchdown point resulting in insufficient runway to stop.
Probable cause
The pilot's failure to perform a missed approach after losing sight of the runway and the misjudgment of distance on the runway which resulted in an overrun. A contributing factor was the fog.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA05LA049
- Event ID
- 20050127X00113
- Case number
- MIA05LA049
- 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: b6b738ff81e1a525b62387bf863535d93b6cb620cd9e4ee4b3200981b9a5d6f4; retrieved 2026-09-22T06:22:10.013Z.