ERA14CA150 · Piper PA-28-140
Julep Arbor Flying Piper PA-28-140 · Accident: aircraft wake turbulence encounter during landing
From Mid-Carolina Regional Airport (RUQ) to Mid-Carolina Regional Airport (RUQ)
Event
- NTSB case
- ERA14CA150
- 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
Piper PA-28-140
- Aircraft type
- Piper PA-28
- 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
- N4335T
- Operator
- Julep Arbor Flying
- Onboard fatalities
- Unknown
- Route
- From Mid-Carolina Regional Airport (RUQ), Salisbury, NCTo Mid-Carolina Regional Airport (RUQ), Salisbury, NC
- Aircraft age
- About 43 years (built 1971)
- 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
- Landing · flare/touchdown
- 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
- Aircraft wake turbulence encounter
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
At the time of the accident, simultaneous operations were being conducted at the airport. Airplanes were in left traffic for landing on runway 20, and military helicopters were in right traffic landing to a midfield helipad on the west (right) side of the runway. According to the flight instructor (CFI) in the accident airplane, the student pilot completed three touch-and-go landings and proceeded around the pattern for a fourth landing. During the landing the airplane approached the runway as a helicopter "suddenly lifted to a hover." Several witness statements and security video revealed that the 2,150-pound airplane followed behind an airplane that landed on the runway, and passed abeam an 18,000-pound Army utility helicopter on final approach to the helipad, before it banked sharply to the right and impacted terrain. Post-accident examination of the airplane by an FAA inspector revealed partial separation of the right wing and substantial damage to the fuselage. The CFI reported there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
According to the FAA's Aeronautical Information Manual, section 7-3-7:
In a slow hover taxi or stationary hover near the surface, helicopter main rotor(s) generate down wash producing high velocity outwash vortices to a distance approximately three times the diameter of the rotor. When rotor downwash hits the surface, the resulting outwash vortices have behavioral characteristics similar to wing tip vortices produced by fixed wing aircraft. However, the vortex circulation is outward, upward, around, and away from the main rotor(s) in all directions. Pilots of small aircraft should avoid operating within three rotor diameters of any helicopter in a slow hover taxi or stationary hover. In forward flight, departing or landing helicopters produce a pair of strong, high-speed trailing vortices similar to wing tip vortices of larger fixed wing aircraft. Pilots of small aircraft should use caution when operating behind or crossing behind landing and departing helicopters.
Probable cause
The flight instructor's decision to continue the landing in close proximity to a landing helicopter, resulting in an encounter with rotor vortices, loss of airplane control, and collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA150
- Event ID
- 20140310X21314
- Case number
- ERA14CA150
- 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. 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: 3c0e9e6a10e08990a4c35817b58f9cf371bf7c77e7290e8a1f2632fc6431ce44; retrieved 2026-09-15T23:22:59.623Z.