Flightstar SC II accident near Painesville, Ohio, July 27, 2018
On July 27, 2018 at about 8:45 pm local time, a 2001 Flightstar SC II, registered N953RJ, was substantially damaged in an accident during initial climb near Painesville, Ohio (Concord Airpark airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The student pilot’s failure to maintain an airspeed below flight speed during a practice taxi run, which resulted in the airplane inadvertently becoming airborne. Once airborne, the reduced engine power due to an improper propeller pitch setting and carburetor icing degraded the airplane’s performance and prevented the airplane from being able to continue to climb.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 27, 2018 · about 8:45 pm local time
- Place
- Painesville, Ohio · Concord Airpark · map
- Type
- Accident
- Injuries
- 1 person was seriously injured and 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Flightstar SC II, built 2001
- Registration
- N953RJ · no longer on the register · serial 325
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student pilot reported that he and his wife owned the accident airplane and had made multiple practice taxi runs on the runway with no intention for flight. During one of the taxi runs, the airplane unexpectedly became airborne. The student determined that there was not enough runway remaining to perform a safe landing, so he chose to continue the takeoff. Once the airplane reached about 100 ft above ground level, it would no longer climb, and he attempted to land in a field; however, the airplane struck trees before reaching the intended field. Before the accident, the student had performed maintenance on the airplane, which included replacing the propeller. He had intended to have a certificated mechanic check his work but had not done so before the accident because there was no intention for flight. He acknowledged that he may not have set the propeller pitch correctly, which could have negatively affected the airplane's performance. In addition, the atmospheric conditions were favorable for moderate icing at cruise power settings and serious icing at descent power settings. Carburetor icing likely accumulated during the multiple taxi runs performed before the unintentional flight. Based on the available information, the airplane inadvertently became airborne because the student allowed it to accelerate to flight speed. The available engine power was likely reduced due to an improper propeller pitch setting and carburetor icing, and both these conditions likely resulted in the airplane's inability to continue to climb.
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
- Other weather encounter during initial climb
- Loss of engine power (partial) during initial climb defining event
- Off-field or emergency landing during landing
- Collision with terrain or object (not controlled flight into terrain) during maneuvering
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Aircraft › Aircraft propeller/rotor › Propeller system › Propeller blade section › Incorrect service/maintenance
- cause Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to carburetor icing › Effect on equipment
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Student/instructed pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Climb rate › Attain/maintain not possible
- Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Contributed to outcome
Pilot
- Certificate: student
- Flight time: 21 hours in all; 0 in this make and model; 9 in the last 90 days; 9 in the last 30 days; 0 as pilot in command; 0 on instruments
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Maximum gross weight: 998 lb
- Seats: 2
- Landing gear: fixed
- Engine: Hks 700E (piston); 0 hours total
The flight
- Departed from: 2G1 Painesville OH at 8:45 pm
- Destination: 2G1 Painesville OH
- Flight plan: none
- Runway 2, 2,181 ft by 38 ft
Weather at the time
- Light: daylight
- Wind: from 310° at 3 knots
- Visibility: 10 statute miles
- Sky: overcast at 11,000 ft; scat at 9,000 ft
- Temperature: 73°F (23°C), dew point 54°F (12°C)
- Altimeter: 29.97 inHg
- Observation at 8:55 pm from LNN, 8 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
1 document, released by the NTSB on January 29, 2019. 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 | Record of Conversation with Pilot | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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.
