DFW06CA014 · Cessna 182J
Cessna 182J · Accident: loss of control in flight during landing
From Mustang Beach Airport (RAS) to Twin-Oaks Airport (T94)
Event
- NTSB case
- DFW06CA014
- 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
Cessna 182J
- Aircraft type
- Cessna 182
- 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
- N3331F
- Operator
- Roman Gomez Jr
- Onboard fatalities
- Unknown
- Route
- From Mustang Beach Airport (RAS), Port Aransas, TXTo Twin-Oaks Airport (T94), San Antonio, 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
- Landing
- 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
- Loss of control in flight
- 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 › Compensation for wind conditions, inadequate
- Pilot in command › Go-around, delayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 435-hour pilot reported that he was attempting to perform a short field landing on runway 30 (2,085-feet long, by 30-feet wide) at an uncontrolled airport. At a nearby airport located two miles south, approach control was reporting winds from the north at 7 knots, gusting between 20 and 25 knots. The pilot reported that with the airplane configured with full flaps, and while maintaining an airspeed of 65 miles per hour, he initiated a landing flare. The pilot attempted to make a correction and apply full power; however, the airplane touched down short of the landing threshold. As the airplane reached the lip of the asphalt landing threshold, the nosewheel strut sheared-off and the airplane skidded off the right side of the runway, colliding with the airport perimeter fence. The pilot reported that there were no mechanical deficiencies with the airplane prior to the accident.
Probable cause
The pilot's failure to compensate for prevailing wind conditions and his delay in executing a go-around. A contributing factor was the gusty winds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA014
- Event ID
- 20051213X01968
- Case number
- DFW06CA014
- 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: 43d538bb39dc34005ee9b8b54b900b01c4d318b3216afd1f84c62ec8a1b9d414; retrieved 2026-09-22T05:16:58.155Z.