Skip to content

Atlas / NTSB / CEN12CA130

NTSB CAROL · Event

Event CEN12CA130

2011-12-28 Eldorado, Texas, United States Airport · 27R None 1 aircraft Status: Completed

Registry · N6129T

FAA Aircraft Registry record.

Make / Model

MAULE M-7-235A

Year of manufacture

1988 · 23 years old at event

Engine

LYCOMING IO-540-W1A5D (235 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

20120711

ADS-B equipped

Yes — Mode-S A7F9D1

Registrant of record

TAF AERIAL SERVICES LLC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's inadequate in-flight planning and decision-making, which resulted in a loss of control during a crosswind landing.

Factual narrative

***This report was modified on February 24, 2012. Please see the docket for this accident to view the original report.*** After checking the weather for the route of flight, the pilot initiated the aerial observation flight to survey pipelines in his tail wheel equipped airplane. The flight was uneventful and the pilot set up to land at his planned airport to refuel. Prior to making the approach to land, the pilot checked the nearest weather reporting facility (about 33 miles to the southwest). The facility reported the wind from 270 degrees at 15 knots, with gusts of 20 knots. The pilot made preparations for a crosswind landing on the runway bearing 350 degrees. On final approach, the pilot noted that the windsock appeared to be extended at a 45 degree angle to the runway. He made his final approach with the upwind wing down and a bit more airspeed than usual to compensate for the crosswind. After both main wheels were on the runway, the pilot felt the upwind wing lift, even with full left aileron and opposite rudder inputs. He also felt that the airplane's right wheel brake was "spongy." As the wing lifted, the airplane began to ground loop to the left and the pilot thought that it was too late to initiate a go-around. The airplane then skidded off the runway, impacting terrain, which resulted in substantial damage to the wings. After the pilot exited the airplane, he noted that the windsock was fully extended perpendicular to the runway. After the accident, the pilot stated that he was very experienced in crosswind landings and that he should have not relied on a distant weather facility report. He stated that he should have made a full pattern approach to check the windsock more closely and better assess the local wind before landing. He stated that if he had been aware of how high the crosswind actually was, he would not have landed at this airport. As the flight neared the destination airport, the pilot obtained information from the nearest weather reporting facility, located about 33 miles away, which indicated that there would be a left crosswind component of about 15 knots with gusts to 20 knots on the landing runway. On final approach, the pilot noted that the windsock appeared to be extended at a 45 degree angle to the runway. He made his final approach with the left wing down and slightly more airspeed than usual to compensate for the crosswind. After both main wheels were on the runway, the pilot felt the left wing lift, even with full left aileron and opposite rudder inputs. He also felt that the airplane's right wheel brake was "spongy." As the wing lifted, the airplane began to ground loop to the left, skidded off the runway and impacted terrain, which resulted in substantial damage to the wings. After the pilot exited the airplane, he noted that the windsock was fully extended perpendicular to the runway. The pilot stated that he was very experienced in crosswind landings and that he should not have relied on a distant weather facility report; rather he should have made a full pattern approach to check the windsock more closely and better assess the local wind before landing. He stated that if he had been aware of how high the crosswind actually was, he would not have landed at this airport. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • Environmental issues-Conditions/weather/phenomena-Wind-Gusts-Contributed to outcome
  • C Personnel issues-Task performance-Planning/preparation-Flight planning/navigation-Pilot - C
  • Environmental issues-Conditions/weather/phenomena-Wind-Crosswind-Contributed to outcome

Verbatim from NTSB's published report. Source file NTSB_2011_CEN12CA130.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (loss of control, go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗