Skip to content

Atlas / NTSB / ERA10CA137

NTSB CAROL · Event

Event ERA10CA137

2010-02-07 Fort Myers, Florida, United States Airport · FMY None 1 aircraft Status: Completed

Registry · N772CT

FAA Aircraft Registry record.

Make / Model

FLIGHT DESIGN GMBH CTLS

Engine

ROTAX 912ULS SERIES (100 hp)

Seats / Engines

2 seats · 1 engine

Last airworthiness date

20090821

ADS-B equipped

Yes — Mode-S AA70B9

Registrant of record

COPPER CITY AVIATION SERVICES LLC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The student pilot's failure to maintain directional control during takeoff.

Factual narrative

The student pilot of the special light-sport airplane stated that he had performed six touch-and-go landings with his certified flight instructor (CFI), and at the completion, his instructor approved him for solo flight. He obtained the automated terminal information service, which indicated the wind was from 320 degrees at 10 knots, and he taxied to runway 31. He began the takeoff roll and felt that the airplane was being pushed from the left. He corrected with rudder input and felt as though he was being pushed back to the right, even though he had corrective rudder input. He applied left rudder input again, but the airplane went off the runway and contacted the ground, nosing over. The student exited the inverted airplane and was not injured. The student’s CFI, who was watching the takeoff, reported that during the takeoff roll the airplane began veering towards the left side of the runway. Briefly, the CFI saw the nose and left main landing gear off the runway about 6 to 12 inches, before seeing them contact the runway surface. The CFI further reported that while on the ground the airplane then collided with a taxiway sign, causing the airplane to nose over. Postaccident inspection of the airplane by a Federal Aviation Administration airworthiness inspector revealed no evidence of preimpact failure or malfunction of the flight controls. The student pilot of the special light-sport airplane stated that he had performed six touch-and-go landings with his certified flight instructor (CFI), and at the completion, his instructor approved him for solo flight. He obtained the automated terminal information service, which indicated the wind was from 320 degrees at 10 knots, and he taxied to runway 31. He began the takeoff roll and felt that the airplane was being pushed from the left. He corrected with rudder input and felt as though he was being pushed back to the right, even though he had corrective rudder input. He applied left rudder input again, but the airplane went off the runway and contacted the ground, nosing over. The student exited the inverted airplane and was not injured. The student’s CFI, who was watching the takeoff, reported that during the takeoff roll the airplane began veering towards the left side of the runway. Briefly, the CFI saw the nose and left main landing gear off the runway about 6 to 12 inches, before seeing them contact the runway surface. The CFI further reported that while on the ground the airplane then collided with a taxiway sign, causing the airplane to nose over. Postaccident inspection of the airplane by a Federal Aviation Administration airworthiness inspector revealed no evidence of preimpact failure or malfunction of the flight controls. 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).

  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Student pilot - C

Verbatim from NTSB's published report. Source file NTSB_2010_ERA10CA137.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. 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 ↗