MIA04FA029 · Swearingen SA-26-AT
Swearingen SA-26-AT · Accident: in flight collision with object on approach
From Beaumont Municipal Airport (BMT) to Jacksonville Executive at Craig Airport (CRG)
Event
- NTSB case
- MIA04FA029
- 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
- 1 · 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
Swearingen SA-26-AT
- Aircraft type
- Swearingen SA-26
- 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
- N698X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Beaumont Municipal Airport (BMT), Beaumont, TXTo Jacksonville Executive at Craig Airport (CRG), 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
- 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 object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Decision height, continued below
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 was on an instrument flight from Beaumont, Texas, to Craig Airport, Jacksonville, Florida. According to the pilot's children who were passengers on the airplane, the pilot knew the destination airport was forecast to have fog upon their arrival. Air traffic controllers informed the pilot east of Tallahassee, Florida, the fog at his destination airport would not lift for at least an hour and a half. The pilot was informed the weather at Saint Augustine, Florida, was clear skies with two miles visibility. The pilot informed the controller that he would slow the airplane and continue to Craig. The pilot was subsequently cleared to descend and provided vectors for the ILS Runway 32 approach at Craig. The pilot informed the controller that he had the current automatic terminal information service (ATIS) information. The ATIS for Craig reported an indefinite ceiling with a vertical visibility of 100 feet, and one-quarter of a mile visibility. The weather minimums for the ILS runway 32 approach is a decision height of 241 feet, and one-half mile visibility. The controller informed the pilot to contact Craig Tower. The pilot contacted Craig Tower, and was instructed to report passing the final approach fix. The controller informed the pilot that Jacksonville International Airport had a runway visual range of more than 6,000 feet, and that airplanes were making it in. The controller asked the pilot what his intentions were in the event he made a missed approach. The pilot replied, "I got my brother bringing my mom there into your airfield, so I do not know, what do you think is best, what's closest." The controller replied Jacksonville was closer than Saint Augustine. The pilot informed the controller that he would go to Jacksonville in the event of a missed approach. The pilot was cleared to land, and there was no further radio contact between the pilot and Craig Tower. The airplane was located a short time later in a wooded area, 1.8 miles from the airport. Postaccident examination of the airplane revealed no preimpact mechanical anomalies.
Probable cause
The pilot's descent below decision height while performing an ILS approach with low ceilings and fog, resulting in an in-flight collision with trees and the ground. A factor associated with the accident was the pilot's decision to attempt the instrument approach with weather below the prescribed minimums.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA04FA029
- Event ID
- 20031202X01981
- Case number
- MIA04FA029
- 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: cb9942d0ed639525ceaa2300527628c23b55f829be62ee1e685adff84e9ea547; retrieved 2026-09-20T18:45:38.395Z.