Piper PA-36-300 accident near Agar, South Dakota, May 23, 1989
On May 23, 1989 at about 12:45 pm local time, a Piper PA-36-300, registered N82644, was destroyed in an accident near Agar, South Dakota. It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). 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 AN ADEQUATE CLEARANCE WITH THE POWERLINES. THE POWERLINE IS CONSIDERED TO BE A CONTRIBUTING FACTOR TO THE ACCIDENT.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 23, 1989 · about 12:45 pm local time · cases in 1989
- Place
- Agar, South Dakota · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-36-300 · all PA-36-300s on the register
- Registration
- N82644 · registry record · serial 36-7760126
- Damage
- Destroyed
- Flight
- Aerial application (crop spraying) flight · agricultural flying rules (Part 137)
The NTSB's narrative final · quoted from the NTSB record
THE PILOT COMPLETED A SMOKE DISPENSING RUN FROM WEST TO EAST ALONG THE NORTH EDGE OF A FIELD TO BE SPRAYED. THERE IS A POWERLINE ALONG THE NORTH EDGE OF THE FIELD. UPON COMPLETION OF THE SMOKE RUN THE PILOT EXECUTED A LEFT TURNAROUND. AT THE COMPLETION OF THE TURNAROUND THE AIRCRAFT COLLIDED WITH THE POWERLINE AND CRASHED.
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
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land
- Flight time: 12,500 hours in all; 50 in the last 90 days; 20 in the last 30 days; 12,400 as pilot in command
- Medical certificate: Class 2 (valid medical--w/ waivers/lim.)
- Seat: frt
The aircraft
- Last inspection: annual inspection, December 9, 1988
- Maximum gross weight: 4,400 lb
- Seats: 1
- Landing gear: fixed
- Engine: Lycoming IO-540-K1 (piston); 0 hours total
The flight
- Departed from: 98D Onida SD at 12:35 pm
- Flight plan: none
- Runway 0
Weather at the time
- Light: daylight
- Wind: from 110° at 5 knots
- Visibility: 35 statute miles
- Sky: clear
- Temperature: 57°F (14°C), dew point 54°F (12°C)
- Altimeter: 29.00 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| 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.
Connections how this case links to the rest of the register
- N82644 on the register today · the tail number may have moved to another aircraft since
- Piper PA-36 Pawnee Brave 99 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Lycoming IO-540-K1 4,223 aircraft carry this series today · as the NTSB recorded it
- Onida Municipal · departed from
- Accidents and incidents in South Dakota 469 since 1982 · 69 in the last ten years
- South Dakota 2,278 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/DEN89DTK01.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.
