FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02CA250 · Piper PA-J3-C65

9 Jul 2002 · Sparta, IL, United States

Piper PA-J3-C65 · Accident: loss of control on ground/water during landing

From Sparta Community Airport - Hunter Field (SAR) to an unrecorded destination

Report a problem

Event

NTSB case
CHI02CA250
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
0 · 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
Visual Meteorological Cond

Piper PA-J3-C65

Aircraft type
Piper PA-J3-C65
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
N7744B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sparta Community Airport - Hunter Field (SAR), Sparta, ILTo not recorded
Aircraft age
Not recorded
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
Landing · landing roll
First occurrenceThe 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
Loss of control on ground/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command(cfi) › Directional control, not maintained
  • Pilot in command(cfi) › Go-around, not successful

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane sustained substantial damage when it impacted a ditch during landing roll. The CFI reported that the flight was an introductory tail wheel instructional flight. He reported, "Student pilot flew aircraft under my direction through several flight maneuvers for initial orientation. He also approached the airport for our initial landing on runway 27 at SAR. Upon turning final for the runway I took full control of the aircraft to demonstrate a 3 point landing. All went well until aircraft started an uncontrollable right turn on the runway. I applied full opposite control but was unable to recover so I chose to initiate a go around but could not gain flying speed before encountering a drainage ditch adjacent to the runway. Power was removed and aircraft was damaged in the drainage ditch."

Probable cause

The CFI's failure to maintain directional control during landing roll and the unsuccessful attempt at a go around. A factor was the ditch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02CA250
Event ID
20020828X01473
Case number
CHI02CA250
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 9ca6692ead130da7ba874b5aa739c0b061e9e6951995c3af3bd8e9c56568ce28; retrieved 2026-09-22T10:44:55.724Z.