FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW08LA231 · Evektor-Aerotechnik AS SPORTSTAR

12 Sept 2008 · Roanoke, TX, United States

North Texas Flight Academy Evektor-Aerotechnik AS SPORTSTAR · Accident: loss of control on ground during takeoff

From Aero Valley Airport (52F) to Aero Valley Airport (52F)

Report a problem

Event

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

Evektor-Aerotechnik AS SPORTSTAR

Aircraft type
Evektor SPORTSTAR
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
N901LA
Onboard fatalities
Unknown
Route
From Aero Valley Airport (52F), Roanoke, TXTo Aero Valley Airport (52F), Roanoke, 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
Takeoff
Defining eventThe 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 on ground
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

After landing for his fifth touch-and-go maneuver, the pilot applied full engine power for takeoff. As he applied engine power the airplane began to swerve towards the left side of the runway. To arrest the swerve the pilot applied right rudder pedal, which resulted in a swerve back to the right. Unable to stop this swerve the airplane exited the right side of the runway. Moments later the airplane's right main landing gear and nose landing gear collapsed. The airplane came to rest in grass alongside the runway in an upright position. The pilot reported that he had previously accumulated 2 flight hours in the accident airplane's make and model. An examination of the airplane after the accident revealed no anomalies that would have prevented normal operation of the airplane's flight controls.

Probable cause

The pilot's failure to maintain directional control of the airplane during the landing roll. Contributing to the accident was the pilot's lack of flight experience in the make and model of airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW08LA231
Event ID
20081003X17331
Case number
DFW08LA231
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: dbab1bb5b9c0bd4d6a069d86f074fd426034e28de08e3797f81ac754e7a9cb98; retrieved 2026-09-15T10:16:50.787Z.