FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

2022 CASA Aviocar accident in North Carolina

29 Jul 2022 · Raeford West Airport, North Carolina, United States

Rampart Aviation CASA C212 · The 2022 CASA Aviocar accident in North Carolina occurred on 29 July 2022

From Raeford West Airport, North Carolina, United States to Raeford West Airport, North Carolina, United States

Report a problem

Event

NTSB case
ERA22LA348
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
Event fatalities
1 · all aircraft and ground
Ground fatalities
0
Occupants
Unknown
Survivors
1
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0 serious · 0 minor (NTSB)
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

CASA C212

Aircraft type
Casa C212
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
N497CA
Onboard fatalities
Unknown
Route
From Raeford West Airport, North Carolina, United StatesTo Raeford West Airport, North Carolina, United States
Aircraft age
About 39 years (built 1983)
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
Approach · VFR go-around
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
Abnormal runway contact
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 structures
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

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

From the Wikipedia article

The 2022 CASA Aviocar accident in North Carolina occurred on 29 July 2022. On that day two pilots were approaching Raeford West Airport in a CASA Aviocar when the aircraft touched down abruptly on the runway, whereupon the landing gear was torn off. The pilots then initiated a go-around. During the second approach the first officer opened the rear cargo ramp, jumped out of the aircraft (presumably with suicidal intent) and fell to his death. The captain was able to make a successful emergency landing with the aircraft, with a “Ringelpiez”, at Raleigh-Durham International Airport.

Accident sequence

Two drop flights had been flown with the aircraft that day. The pilots were on the flight to Raeford to pick up parachutists for a third time. The aircraft was being flown by the first officer on the flight. On the first approach the aircraft descended below the minimum safe altitude and struck the runway, whereupon the pilots initiated a go-around. The aircraft was badly damaged in the process; the right main landing gear was sheared off. The pilots climbed the aircraft to a height of 400 feet and flew low over runway 20 so that the airport personnel on the ground could inspect the damage to the aircraft caused by the crash landing. The air traffic controllers at Raeford West informed the captain that the torn-off right main landing gear had been recovered from the runway. The captain then instructed the first officer to declare an emergency and to request an emergency landing at Raleigh-Durham International Airport. On the flight to Raleigh the pilots coordinated the approach and landing with the air traffic control there, with the first officer responsible for radio communications and the captain flying the aircraft.

The captain later reported that there was light turbulence on the flight. The first officer received the instructions for the approach and the emergency landing from air traffic control in Raleigh. About 20 minutes after the pilots had turned back towards Raleigh, the first officer had appeared visibly depressed because of the emergency landing. He had opened the side cockpit window. The captain expressed the assumption that the first officer had possibly become sick at this point. The captain took over radio contact with air traffic control, while the first officer opened the rear ramp, which suggested that he had become sick and needed to get some air. The first officer had then stood up, taken off his headset and excused himself. He had then gone to the rear ramp and jumped out of the aircraft through it. The captain had then flown a right turn to look out for the first officer, but eventually he had continued the flight to Raleigh, where he carried out a low-altitude approach and the emergency landing. During the emergency landing the aircraft veered off the runway to the right and came to a stop in the grass.

Accident investigation

The accident investigation revealed considerable damage to the right main landing gear, its attachment points and to the fuselage in the area where the attachment points are located.

The captain later stated that six feet above the ramp there was a bar that could be grabbed when jumping out of the aircraft. The captain stated for the record that he was not able to observe the first officer using this bar.

Translated into English with AI assistance from the German Wikipedia article “Flugunfall einer CASA Aviocar in North Carolina 2022” (revision 252290423, retrieved 2026-09-19) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out; the translation may contain errors, and long articles were cut to their first 700 words. Read the article

NTSB narrative

After dropping a load of skydivers, the pilots were returning to the airport to pick up another group of skydivers, with the second-in-command (SIC) as the pilot flying. The pilot-in-command (PIC) indicated that the approach was stabilized until the airplane descended below the tree line and encountered what he described as windshear. The SIC initiated a go-around; however, before he could arrest the airplane’s sink rate and establish a climb, the right main landing gear impacted the runway surface and separated from the airplane. The crew declared an emergency, reported the loss of the right wheel, and requested to divert to a larger airport. During this diversion, the crew planned the landing, and the SIC communicated with air traffic control (ATC) while the PIC flew the airplane. The PIC reported that, about 20 minutes into the diversion, after conducting approach and emergency briefings, the SIC became visibly upset following the hard landing. The PIC described that, about this time, the SIC opened his side cockpit window and lowered the ramp in the back of the airplane, indicating that he felt like he was going to be sick and needed air. The PIC stated that the SIC looked at him and said he was sorry, got up from his seat, removed his headset, and ran out of the airplane via the aft ramp door. The PIC subsequently notified the controller that the copilot had just jumped out of the back of the airplane without a parachute. The PIC subsequently performed a successful emergency landing. Although the PIC and operator reported that the SIC’s departure from the airplane was an intentional act, there was insufficient information to support that assertion. No family or company personnel shared concerns about the SIC’s state of mind or behavior until the events that resulted in his departure from the aircraft; however, a company pilot shared an event during which the SIC had seemed to have a disproportionate, intense emotional and physical reaction upon becoming worried that he had lost a fuel payment card. The operator and family also indicated that the SIC felt that the accident flight with the PIC, who was also the chief pilot for the operator, was very important. This would have added to the SIC’s stress and emotional response after the hard landing, during which he was the pilot flying. In the 20 minutes of flight while serving as the monitoring pilot, the SIC was actively engaged in communicating with ATC, reviewing emergency procedures, and providing recommendations to the PIC on the landing runway at the diversion airport. In his initial statement to authorities, the PIC stated that, before departing the airplane, the SIC became visibly upset and apologetic, and reported feeling sick. His actions to increase ventilation in the cabin, which included opening the window and lowering the ramp, as well as his hurried departure from his seat, are consistent with an attempt to address increasing nausea symptoms and a desire to not throw up in the cockpit. However, the SIC made an unsafe decision to run to the rear of the cabin with the ramp in a fully lowered position, as he likely had not previously been in the cabin in flight with the ramp down. It is possible in his haste he lost his footing when encountering the area of the ramp and inadvertently fell from the airplane. Weather sounding and radar data supported the potential for windshear and turbulence activity, and the PIC reported that there had been moderate turbulence during the flight. The postaccident toxicological finding of mitragynine in the SIC’s liver tissue and urine indicated that he had used a kratom product, which had the potential to cause impairment. Notably, anxiety control was a common motivation for kratom use, and anxiety itself may predispose people to heightened physiological responses to stress, which sometimes manifest with nausea, dizziness, or feeling hot or smothered. Although it is possible that effects of kratom may have contributed to nausea or to some dizziness or perceptual impairment that may have increased his risk of falling, there is insufficient evidence to determine whether effects of the SIC’s kratom use contributed to the accident.

Probable cause

The airplane’s encounter with windshear during landing, which resulted in a hard landing and separation of the right main landing gear, and the pilot’s subsequent decision to leave his seat in flight, which resulted in his fall from the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

German Wikipedia article: Flugunfall einer CASA Aviocar in North Carolina 2022
Article
Flugunfall einer CASA Aviocar in North Carolina 2022
Translation
Into English with AI assistance; names of linked operators and aircraft types from Wikidata. It may contain errors.
Revision
252290423 · 2025-01-15 · retrieved 2026-09-19
Wikidata
Q120907326
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record ERA22LA348
Event ID
20220801105636
Case number
ERA22LA348
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
de Wikipedia article "Flugunfall einer CASA Aviocar in North Carolina 2022" (page 12578896, revision 252290423), translated into English with AI assistance; merged with NTSB case ERA22LA348 (events / aircraft)
Date
NTSB record ERA22LA348: NTSB API eventDate, eventTimeUtc and eventTimeUtcOffsetHours (local date)
Place and country
Wikipedia infobox: site; country from NTSB record ERA22LA348
Map position
NTSB record ERA22LA348: NTSB API eventLatitude/eventLongitude
Aircraft, operator and route
NTSB record ERA22LA348: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record ERA22LA348: operated under Part 91: General Aviation
Fatalities
NTSB record ERA22LA348: NTSB API totalFatal
Ground fatalities
NTSB record ERA22LA348: NTSB API ongroundFatal
Summary
Wikipedia article lead
Source notes (3)
  • One occurrence in two sources, merged: the Wikipedia article "2022 CASA Aviocar accident in North Carolina" and NTSB case ERA22LA348, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. 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.