Piper TITAN TORNADO II D accident near Ravenna, Ohio, December 3, 2017
On December 3, 2017 at about 4:40 pm local time, a 2017 Piper TITAN TORNADO II D, an amateur-built aircraft,, registered N2200T, was destroyed in an accident during approach (VFR pattern final) near Ravenna, Ohio (Portage County Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain adequate airspeed following a loss of engine power during final approach for landing, which resulted in an exceedance of the airplane's critical angle of attack and an aerodynamic stall.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 3, 2017 · about 4:40 pm local time · cases in 2017
- Place
- Ravenna, Ohio · Portage County Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper TITAN TORNADO II D, built 2017, amateur-built
- Registration
- N2200T · no longer on the register · serial 002
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The sport pilot of the experimental, amateur-built airplane was returning to the airport after a 30-minute flight. A witness saw the airplane on final approach to the runway about 500 ft above ground level when he heard a total loss of engine power. The airplane banked left and right and entered a nose-down descent consistent with an aerodynamic stall condition. The airplane impacted terrain short of the runway. Although the witness, an acquaintance of the accident pilot, estimated that the pilot had accrued about 10 hours of flight time in the airplane since purchasing it about 1 year prior, the pilot's logbook was not located during the investigation, and his experience level in the accident airplane could not be determined. Additionally, it could not be determined if the pilot had obtained transition training in the accident airplane, which was classified as a low-inertia/high-drag airplane. Low-inertia/high-drag airplanes rapidly lose energy (airspeed and/or altitude) when there is a loss or reduction of power, and are particularly susceptible to unintentional aerodynamic stalls due to their low cruise speed to stall speed margin and their tendency to experience significant airspeed decay with increased load factor (such as during a turn). Examination of the airplane and engine revealed no mechanical anomalies that would have precluded normal operation; therefore, the reason for the loss of engine power could not be determined. It is likely that the pilot failed to attain a proper airspeed following the loss of engine power, which resulted in an exceedance of the airplane's critical angle of attack, an aerodynamic stall, and impact with terrain.
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 engine power (total) during approach (VFR pattern final)
- Loss of control in flight during approach (VFR pattern final) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Attain/maintain not possible
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: sport pilot
- Ratings: single-engine land
- Medical certificate: Sport Pilot (without waivers/limitations)
- Seat: frt
- Injury: fatal
The aircraft
- Last inspection: condition inspection, February 6, 2017; 0 hours since
- Seats: 2
- Landing gear: fixed
- Engine: Jabiru 2200 (piston); 0 hours total
The flight
- Departed from: POV Ravenna OH at 4:10 pm
- Destination: POV Ravenna OH
- Flight plan: none
- Runway 27, 3,499 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 270° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 43°F (6°C), dew point 32°F (0°C)
- Altimeter: 30.21 inHg
- Observation at 3:33 pm from POV, 1 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 NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Connections how this case links to the rest of the register
- N2200T: not on the register today · the record of its deregistration
- Piper 44,844 aircraft on the register
- Engine: Jabiru 2200 147 aircraft carry this series today · as the NTSB recorded it
- Portage County · nearest airport
- Accidents and incidents in Ohio 1,884 since 1982 · 253 in the last ten years
- Ohio 8,534 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN18FA045.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
