CEN24FA326 · Rans S19
Rans S19 · Accident: VFR encounter with IMC en route
From Karl Stefan Memorial Airport (OFK) to an unrecorded destination
Event
- NTSB case
- CEN24FA326
- 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
- 1 · 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
- Instrument Meteorological Cond
Rans S19
- Aircraft type
- Rans S19
- 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
- N519JR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Karl Stefan Memorial Airport (OFK), Norfolk, NETo not recorded
- Aircraft age
- About 2 years (built 2022)
- 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
- En route · cruise
- 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
- VFR encounter with IMC
- 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
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane departed in daylight, visual weather conditions and proceeded along a meandering flight path before heading towards Yankton, South Dakota, for an unknown destination. About an hour after departure, while over Yankton, the pilot made a telephone call to a friend to inquire about the weather and airport options, stating that he was unable to land due to the weather as he did not hold an instrument rating. The pilot was not instrument rated, the airplane was equipped for only visual flight rules (VFR) operations, and the weather conditions at the nearby airport included a cloud ceiling at 200 ft above ground level (agl) with 1/4-mile visibility in fog and light rain. The friend suggested two airports south of the pilot’s position with automated weather stations reporting VFR weather conditions. The friend also stated that the pilot seemed calm and did not mention if he was in instrument meteorological conditions (IMC). A NTSB weather study determined that a cold front and inversion in the area, along with low- and mid-level troughs, made for an environment conducive to sustained low-level cloud cover, moisture, and precipitation. A review of recovered flight track data from an onboard GPS unit revealed that about the time that the pilot called his friend, the airplane was at an altitude of 3,239 ft mean sea level (msl) tracking roughly southwest. The flight track remained consistent during the next 8 minutes for about 14 nm, suggesting that the pilot was in VFR conditions above the cloud tops. The airplane then began a right turn to the west with a slow climb to a maximum altitude of about 4,000 ft msl. About 1 minute later, the airplane began an S-turn, followed by a descending left turn for less than a minute before the data was lost. The accident site was located about 3/4 nm northeast of the last data point. The weather study determined that the accident flight was likely in IMC from 3,500 ft msl down to 200 ft agl, with visibility restricted to 1/4 mile or less below the cloud cover. The study also noted that a band of rain showers was moving northeast across the accident site at the accident time, which likely further reduced visibility below the cloud layer and had associated convective turbulence. A postaccident examination of the airplane revealed no evidence of mechanical malfunction or failure that would have precluded normal operation. However, flight control continuity could not be established due to impact damage. It is unknown what, if any, weather information the pilot checked before or during the flight, or whether the nearby airport (at the time that the pilot called his friend) was the intended destination. However, the reported weather at that airport from more than 2 hours before the accident flight departed through the time of the accident consistently included low instrument flight rules (LIFR) conditions. (LIFR is defined as a ceiling below 500 ft agl and/or visibility less than 1 mile.) The weather forecast information applicable for the accident time did not include any graphical or text AIRMETs for instrument flight rules (IFR) conditions, and no terminal aerodrome forecasts were available within 30 miles of the accident site. The National Weather Service (NWS) graphical forecast analysis products issued more than 3 hours before the accident flight departed forecast LIFR surface visibility for the area of the accident applicable about 1 hour 40 minutes before the accident and VFR surface visibility with a cloud ceiling at 2,300 ft msl (about 600 ft agl) for the area of the accident applicable about 1 hour 20 minutes after the accident. The weather conditions encountered by the accident pilot were worse than NWS forecasts valid for the accident time. Several pilot reports (PIREPs) reported cloud tops between 2,600 ft MSL and 3,500 ft MSL in the area. Loss of external visual references during VFR flight presents a high risk of spatial disorientation and loss of control. Several risk factors for spatial disorientation were present in this accident: the lack of IFR flight instruments, the non-instrument rated pilot, and the weather conditions. Based on these factors, as well as the airplane’s flight track and the orientation and fragmentation of the wreckage consistent with a high-energy impact, the pilot likely experienced spatial disorientation after entering an area of rain, convective turbulence, and IMC which may have been higher than the surrounding cloud tops, and he subsequently lost control of the airplane.
Probable cause
The non-instrument-rated pilot's decision to continue visual flight into an area of low cloud cover and precipitation which resulted in an inadvertent encounter with instrument meteorological conditions and a loss of control due to spatial disorientation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24FA326
- Event ID
- 20240826194999
- Case number
- CEN24FA326
- 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, 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.
- API snapshot SHA-256: 9fd0abe627f4ab01ddf2811094a6eb4c8eb068b773ea520964df57147676228e; retrieved 2026-09-15T08:56:49.455Z.