FTW03FA059 · Beech 1900C
Raytheon Aircraft Comapany Beech 1900C · Accident: in flight collision with terrain/water on approach
From Beech Factory Airport (BEC) to M39 · Mena, KS
Event
- NTSB case
- FTW03FA059
- 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
- 3 · 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 1900C
- Aircraft type
- Beechcraft 1900
- 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
- N127YV
- Operator
- Raytheon Aircraft Comapany
- Onboard fatalities
- Unknown
- Route
- From Beech Factory Airport (BEC), Wichita, KSTo M39 · Mena, KS
- 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
- 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 › Altitude/clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The aircraft collided with mountainous terrain in a level descent during a visual approach to the destination airport. According to recorded radar data, 10 minutes after descending from 15,000 feet, the flight impacted about 200 feet below the top of the partially obscured ridgeline (elevation of 2550 feet), and 8 miles from the destination. The data indicates the flight path was similar to the global positioning satellite (GPS) approach to the airport. Six minutes before the accident, and the pilot's last transmission to air traffic control, he was informed and acknowledged that radar service was terminated. The flight was 12.4 miles from the accident site when radar contact was lost. Reduced visibility due to fog hampered search & rescue efforts, and the aircraft wreckage was located the next day. The aircraft was equipped with a GPS navigation system; however the installation was incomplete, restricting its use to visual flight rules (VFR) only. The investigation did not determine if the GPS was being used at the time. A non-enhanced Ground Proximity Warning System was also installed. The maximum elevation figure listed on the sectional aeronautical chart covering the area of the accident site and destination airport was 3000 feet mean sea level. The chart also shows an advisory for the area to use caution due to rapidly rising.
Probable cause
In-flight collision with terrain due to the pilot's failure to maintain clearance and altitude above rapidly rising terrain while on a VFR approach. Contributing factors were the obscuration of the terrain due to clouds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW03FA059
- Event ID
- 20021230X05644
- Case number
- FTW03FA059
- 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: dcdade3ee50e7b233c74846d37852cc238db0243475348537b273b34bdee7d66; retrieved 2026-09-20T19:34:59.435Z.