Aviation Charter Beech A100 accident
Beech A100 · Accident: in flight collision with terrain/water on approach
From Flying Cloud Airport (FCM) to City of Colorado Springs Municipal Airport (COS)
Event
- NTSB case
- FTW98FA074
- 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
- 2 · 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
- Charter & commuter
- 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 A100
- Aircraft type
- Beechcraft 100
- 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
- N100BE
- Operator
- Aviation Charter
- Onboard fatalities
- Unknown
- Route
- From Flying Cloud Airport (FCM), EDEN PRAIRE, MNTo City of Colorado Springs Municipal Airport (COS)
- 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 135: Air Taxi & Commuter
- 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 missed 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
- Destroyed
Cause areas
- Pilot in command › IFR procedure, not followed
- Pilot in command › Minimum descent altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was cleared for an ILS DME approach to runway 17L. During the final stage of the approach, the aircraft entered fog and disappeared from view of the control tower personnel. Radar and radio communications were lost also. After searching for 31 minutes, the aircraft was found by airport operations personnel over half way down the runway and 600 feet east of the runway. There was no evidence the aircraft touched down on the runway. The aircraft was configured with the landing gear up and the flaps deployed. Missed approach procedures require the flaps and landing gear to be retracted after initiating the procedure. The decision height for the approach is 6,384 feet msl (200 feet above ground level) and the required RVR for a 14 CFR Part 135 flight to commence and approach is 2400 (1/2 mile). When on the glide slope, the decision height is 0.4 miles from the runway touchdown zone. Examination of the airplane did not disclose evidence of mechanical malfunction..
Probable cause
Failure of the pilot to follow IFR Procedures and maintain the minimum descent altitude (MDA). A related factor was fog.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98FA074
- Event ID
- 20001208X09302
- Case number
- FTW98FA074
- 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: e5148e3ddb5fb8813a7986abd341f2840b6f8df5620ce0b3bfdf8e8692b8bb90; retrieved 2026-09-18T13:26:35.258Z.