ERA15CA045 · Beech V35B
J & J Aviation Beech V35B · Accident: runway excursion during landing
From Mount Pleasant Regional Airport Faison Field (LRO) to Vicksburg Municipal Airport (VKS)
Event
- NTSB case
- ERA15CA045
- 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
Beech V35B
- Aircraft type
- Beechcraft 35
- 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
- N4212S
- Operator
- J & J Aviation
- Onboard fatalities
- Unknown
- Route
- From Mount Pleasant Regional Airport Faison Field (LRO), Mount Pleasant, SCTo Vicksburg Municipal Airport (VKS), Vicksburg, MS
- Aircraft age
- About 38 years (built 1976)
- 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 · landing roll
- 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
- Runway excursion
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
As the pilot entered the traffic pattern at the destination airport, the reported wind was variable in direction at a speed of about 5 knots. He also observed that the airport windsock was shifting variably by 180 degrees. The pilot conducted the final approach to the runway with right wind correction applied, but just before touchdown, the wind suddenly shifted to the left, and the airplane oriented right of the runway centerline. The pilot elected to continue rather than abort the landing, and the airplane touched down partially pointed right of the runway centerline. The airplane then departed the right side of the runway, and before the pilot could correct the airplane's track, the right wing stuck a precision approach path indicator light, resulting in substantial damage. The pilot reported that there were no pre-impact mechanical failures or malfunctions of the airplane that would have precluded normal operation.
Probable cause
The pilot's failure to maintain directional control while landing in variable wind conditions, resulting in a runway excursion and collision with an object.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15CA045
- Event ID
- 20141106X72021
- Case number
- ERA15CA045
- 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: f9c67589f481993dc548fe19f7307de835ae160538dd3f6b62c5f9e58e09e6fb; retrieved 2026-09-16T01:55:04.044Z.