FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12CA302 · Evektor-Aerotechnik AS SPORTSTAR

25 Apr 2012 · Lancaster, PA, United States

Sportstar 505EV Evektor-Aerotechnik AS SPORTSTAR · Accident: loss of control on ground during takeoff

From Lancaster Airport (LNS) to Lancaster Airport (LNS)

Report a problem

Event

NTSB case
ERA12CA302
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
N505EV
Onboard fatalities
Unknown
Route
From Lancaster Airport (LNS), Lancaster, PATo Lancaster Airport (LNS), Lancaster, PA
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 › Action/decision
  • 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 the pilot applied full engine power for takeoff, the airplane veered to the left. The pilot attempted to apply right rudder, but was unsuccessful in regaining control of the airplane before it departed the runway surface. The airplane bounced several times as it continued across the grassy area adjacent to the runway and a taxiway before it came to a stop. During the accident sequence the firewall was substantially damaged. Examination of the airplane's rudder and nosewheel steering system revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation.

Probable cause

The pilot's loss of directional control during the takeoff, and her delayed remedial action in aborting the takeoff after the loss of directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12CA302
Event ID
20120426X55701
Case number
ERA12CA302
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: ff02ba6cd8b6342705892ea44c3b17bcb9b5ddc6c57c01e8b2b4c48bc386f089; retrieved 2026-09-15T17:53:07.834Z.