FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW06CA129 · Mahoney Evans VP-1

18 May 2006 · Corpus Christi, TX, United States

Mahoney Evans VP-1 · Accident: in flight encounter with weather during initial climb

From Dean Airport (69TA) to Corpus Christi, TX

Report a problem

Event

NTSB case
DFW06CA129
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
Visual Meteorological Cond

Mahoney Evans VP-1

Aircraft type
Mahoney EVANS VP-1
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
N72260
Operator
Unknown
Onboard fatalities
Unknown
Route
From Dean Airport (69TA), Corpus Christi, TXTo Corpus Christi, 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
Initial climb
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 encounter with weather
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 › Aircraft control, 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 206-hour private pilot reported that he had just taken off from runway 17 at a private airstrip when "at approximately 100 feet above ground level (AGL), a gust of wind from the left blew the airplane knife edge." The pilot stated that he "attempted to correct with hard left rudder and left stick." However, at the time he applied the corrections the gust of wind had subsided and he began to enter a "slow left spiral." The pilot added that he made several attempts to stop the spin; however, he was unsuccessful and the aircraft impacted the ground in a left wing low, nose down attitude. The pilot reported that there were "dust devils" in the area prior to takeoff and that he thought he had encountered one and overcorrected. According to the pilot, the engine and flight controls were functioning correctly, at the time of the accident. The automated weather observation facility at located approximately 7 nautical miles north of the accident site reported winds from 200 degrees at 13 knots, gusting to 17 knots.

Probable cause

The pilot's failure to maintain control of the airplane. A contributing factor was the dust devil/whirlwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW06CA129
Event ID
20060627X00830
Case number
DFW06CA129
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: 540fa9f543175b51f5b9069e5b5abb58794e61f8f685a47eda8953fd33104234; retrieved 2026-09-21T18:46:26.553Z.