Rans S19 accident near Crofton, Nebraska, August 26, 2024
On August 26, 2024 at about 1:41 pm local time, a 2022 Rans S19, an amateur-built aircraft,, registered N519JR, was destroyed in an accident during enroute (cruise) near Crofton, Nebraska. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 26, 2024 · about 1:41 pm local time
- Place
- Crofton, Nebraska · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Rans S19, built 2022, amateur-built · all S19s on the register
- Registration
- N519JR · registry record · serial 090800032
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- VFR encounter with IMC during enroute (cruise) defining event
- Loss of control in flight during enroute (cruise)
- Turbulence encounter during enroute (cruise)
- VFR encounter with IMC during uncontrolled descent
The NTSB's findings
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Pitch control › Not attained/maintained
- Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 1,471 hours in all; 24 in the last 90 days; 7 in the last 30 days; 1,409 as pilot in command
- Last flight review: May 22, 2024
- Medical certificate: BasicMed
- Seat: unk
- Injury: fatal
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 1,320 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912UL (piston); 0 hours total
The flight
- Departed from: OFK Norfolk NE at 12:32 pm
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 300° at 5 knots
- Visibility: 0.2 statute miles
- Sky: broken clouds at 200 ft
- Temperature: 75°F (24°C), dew point 75°F (24°C)
- Altimeter: 30.02 inHg
- Observation at 8:25 am from KYKN, 15 miles away
Weather report (METAR): KYKN 261325Z AUTO 30005KT 1/4SM -RA FG BKN002 OVC019 24/24 A3002 RMK AO2 RAB17 P0000 $
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – Accident Site Overview
Photograph 2 – Fuselage and Empennage
Photograph 3 – Forward Fuselage, Cockpit, and EngineThe NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
14 documents, released by the NTSB on July 16, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Accident Flight Kml | map file · our copy | Download |
| 2 | Witness Mor | PDF, 1 page · our copy | View Download |
| 3 | Examination Summary | PDF, 8 pages · our copy | View Download |
| 4 | Photo Array | PDF, 4 pages · our copy | View Download |
| 5 | Site Diagram | PDF, 1 page · our copy | View Download |
| 6 | Pilot Logbook | PDF, 13 pages · our copy | View Download |
| 7 | Weather Factual Report | PDF, 39 pages · our copy | View Download |
| 8 | Weather Attachment 1 | spreadsheet · our copy | Download |
| 9 | Weather Attachment 2 | GIF file · our copy | Download |
| 10 | Weather Attachment 3 | GIF file · our copy | Download |
| 11 | On Scene Weather Still Frame | PDF, 2 pages · our copy | View Download |
| 12 | GPS - Specialista��s Factual Report | PDF, 7 pages · our copy | View Download |
| 13 | GPS - Attachment 1 | data file · our copy | Download |
| 14 | Toxicological Report | PDF, 1 page · our copy | View Download |
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
