Jabiru J230-SP accident near Reno, Nevada, August 18, 2009
On August 18, 2009 at about 4:50 pm local time, a Jabiru J230-SP, registered N690J, was substantially damaged in an accident during takeoff near Reno, Nevada (Reno Stead airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain directional control throughout the takeoff roll.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 18, 2009 · about 4:50 pm local time
- Place
- Reno, Nevada · Reno Stead · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Jabiru J230-SP
- Registration
- N690J · no longer on the register · serial 654
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that he was taking off for a local flight in the traffic pattern. During the takeoff roll, the nose of the airplane rose up and blocked the runway centerline markings. He stated that the airplane drifted to the left edge of the runway, and he attempted to continue the takeoff. The airplane exited the left side of the runway surface, and impacted terrain. The airplane came to rest in a level attitude. Examination of the airplane by a Federal Aviation Administration inspector revealed structural damage to the nose landing gear assembly, left and right main landing gear assemblies, fuselage, and wing.
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
- Loss of control on ground during takeoff defining event
- Runway excursion during takeoff
- Collision with terrain or object (not controlled flight into terrain) during takeoff
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: sport pilot
- Ratings: single-engine land
- Flight time: 79 hours in all; 46 in this make and model; 63 in the last 90 days; 6 in the last 30 days; 42 as pilot in command
- Last flight review: June 30, 2009
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 61 hours
- Last inspection: condition inspection, July 10, 2009
- Maximum gross weight: 1,320 lb
- Seats: 2
- Landing gear: fixed
- Engine: Jabiru 3300 (piston); 0 hours total
The flight
- Departed from: RST Reno NV at 5:15 pm
- Destination: RST Reno NV
- Flight plan: not recorded
- Runway 08, 7,608 ft by 150 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: a few clouds at 25,000 ft
- Temperature: 73°F (23°C), dew point 27°F (-3°C)
- Altimeter: 30.14 inHg
- Observation at 4:55 pm from KRNO, 11 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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.