FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW06LA088 · Beech C23

21 Mar 2006 · Mena, AR, United States

Beech C23 · Accident: in flight collision with terrain/water while maneuvering

From Mena Intermountain Municipal Airport (KMEZ) to Commerce Municipal Airport (K2F7)

Report a problem

Event

NTSB case
DFW06LA088
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

Beech C23

Aircraft type
Beechcraft 23
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
N2160W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mena Intermountain Municipal Airport (KMEZ), Mena, ARTo Commerce Municipal Airport (K2F7), Commerce, TX
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
Maneuvering
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
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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 › VFR flight into imc, continued

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The 1,042-hour commercial pilot and the pilot rated passenger had flown into the airport in separate airplanes. The pilot rated passenger needed to leave his airplane at a facility to be painted, and the pilot was planning to fly the pilot rated passenger back to his home airport. Prior to taking off, a witness, who worked at the airport, talked to the pilot about delaying his departure due to the low cloud layer that surrounded the airport, and even offered to drive them home. The witness sensed the pilot was in a "hurry", so he suggested that if the pilot was going to depart, he would need to takeoff on the northeast runway, head east, and climb to an altitude of 4,000 feet to clear rising terrain. Shortly after, the witness observed the airplane taxiing to the runway. About 10 minutes later he got a call from the pilot rated passenger saying they had "crashed the airplane on a mountainside." The passenger said, that after they took off, they flew for approximately 8 miles before making a left turn toward the west. The pilot remained on this heading for approximately 10 miles and tracked the highway, that traveled through a valley. As they entered the valley, the passenger (who was using his handheld GPS) informed the pilot that they needed to climb to a higher altitude so they would clear the mountainous terrain that surrounded them. When the airplane reached a certain point in the valley, the pilot made a left turn toward the south proceeded toward a low point along the ridgeline of a mountain. The airplane entered the cloud layer and subsequently collided with terrain about 200 feet below the ridgeline. A witness, who was walking along the highway, observed the airplane flying "very low" in a westerly direction between two mountains. He then observed the airplane turn toward the south and disappear into "heavy fog." Moments later, the witness heard a "loud bang." A review of FAA records revealed that the pilot did not obtain a weather briefing or file an IFR flight plan prior to their departure. According to published airport information, pilots were informed about the mountains located to the north and south-southwest of the airport. In addition, a review of the Memphis Sectional Aeronautical Chart, revealed a warning to pilots stating: "Rapidly Rising Terrain-Use Caution During Periods of Low Ceiling and Visibility." Weather reported at the airport included wind from 280 degrees at 11 knots gusting to 17 knots, visibility 10 statue miles, and an overcast layer at 1,200 feet.

Probable cause

The pilot's continued flight into instrument meteorological conditions. Contributing factors were the mountainous terrain and the low ceilings.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW06LA088
Event ID
20060404X00388
Case number
DFW06LA088
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: a8be81de62b8ee9671d07917bfc354e68b2800a7956dd0aa869e32682897476f; retrieved 2026-09-20T17:28:40.575Z.