ERA20LA150 · Arion Aircraft LLC Lightning LS-1
Arion Aircraft LLC Lightning LS-1 · Accident: controlled flight into terrain/object (CFIT) during initial climb
From Myrtle Beach International Airport (MYR) to Mount Pleasant Regional Airport Faison Field (LRO)
Event
- NTSB case
- ERA20LA150
- 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
- 2 · 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
Arion Aircraft LLC Lightning LS-1
- Aircraft type
- Arion LIGHTNING LS-1
- 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
- N81DJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Myrtle Beach International Airport (MYR), Myrtle Beach, SCTo Mount Pleasant Regional Airport Faison Field (LRO), Mount Pleasant, SC
- Aircraft age
- About 11 years (built 2009)
- 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
- Initial climb
- 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
- Controlled flight into terrain/object (CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The student pilot and flight instructor flew to a nearby airport where they planned to practice touch-and-go landings at night. Flight track data showed that the airplane entered a descending left turn on final approach to the runway at the destination airport. A witness reported hearing a possible airplane accident and the wreckage was subsequently located in trees bordering the south airport security fence. The wreckage path was about 250 ft long and oriented heading away from, and slightly left of the runway departure end centerline; the wreckage was heavily fragmented, consistent with a high-energy impact. A postaccident examination of the flight controls and engine did not reveal any evidence of preimpact anomalies that would have precluded normal operation. At the time of the accident, the weather was reported to be few clouds at 4,400 ft and scattered clouds at 5,500 ft. The departure end of the runway was surrounded by 75- to 100-ft-tall trees about 1,700 ft from the runway edge. Beyond the trees were some residential areas and a highway, followed by a swamp, inlet bay, and the Atlantic Ocean, which was about 2 1/2 miles from the airport. Dark night conditions existed at the time of the accident; the end of civil twilight was about 45 minutes before the accident, and the moon was below the horizon and set to rise about 50 minutes after the accident occurred. Based on autopsy findings, both the student pilot and the flight instructor had moderate coronary artery disease. While cardiovascular disease will increase the risk for an acute cardiac event, there was no evidence to suggest such an event occurred. In this case, there were also two pilots who had the ability to operate the plane if one were to become incapacitated. Based on available information, it could not be definitively determined which of the two pilots was flying the airplane at the time of the accident; however it is most likely that the student pilot, who had recently purchased the airplane, was flying with the flight instructor monitoring the flight. The circumstances of this accident are consistent with the pilot experiencing spatial disorientation, and most likely a somatogravic illusion. During the transition from the landing to the takeoff, the pilot may have interpreted acceleration cues accompanying the takeoff and initial climb as an indication that the airplane was in an abnormally high nose-up pitch attitude. Pilots experiencing this illusion make control inputs to reduce pitch, which can increase acceleration and exacerbate the illusion, leading to a failure to climb or inadvertent descent into terrain. The dark night conditions and limited cultural lighting along the flightpath would have made it difficult for the pilot to recognize that the airplane was not climbing after takeoff using external cues; the pilot likely perceived that the nose of the airplane was pitching up due to the forward linear acceleration, which caused him to push the control yoke forward. The airplane subsequently impacted the trees at high speed off the end of the runway.
Probable cause
The pilot's failure to maintain clearance from trees at the end of the runway due to spatial disorientation during initial climb in dark night conditions. Also causal was the flight instructor’s inadequate monitoring, which did not identify and prevent the descent and subsequent collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA150
- Event ID
- 20200410X81131
- Case number
- ERA20LA150
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2020-04-10.
- API snapshot SHA-256: fab8e07554b1c41e3e7590c011efaa499f943356217e21bb3498fabae6fe1595; retrieved 2026-09-15T07:13:35.933Z.