The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB CHI00LA209 · Final report

Piper PA-28-181 accident near Ashland, Wisconsin, July 16, 2000

On July 16, 2000 at about 7:15 pm local time, a Piper PA-28-181, registered N24GK, was substantially damaged in an accident near Ashland, Wisconsin (John F. Kennedy Memorial airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

the blocked lubricating system and unsuitable terrain.

Source: NTSB aviation accident database, copy made September 29, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 16, 2000 · about 7:15 pm local time
Place
Ashland, Wisconsin · John F. Kennedy Memorial · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-181 · all PA-28-181s on the register
Registration
N24GK · registry record · serial 2843335
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The airplane began to lose engine power during a cruise climb from an island based airport. Power was regained and the pilot diverted to an airport located 8.5 nm to the south at an altitude of 2,600 msl. Five miles from the airport, the engine began to run rough and the pilot began flying best glide airspeed. At 3.5 nm from the airport, smoke emanated from the engine cowling at which point the engine seized. The airplane impacted a barbed wire fence 200 yards from the approach end of the runway 20. Examination of the Textron Lycoming O-360-A4M engine revealed an abrasive material, similar to that used during the engine manufacturing process, was present in the oil passages from the main gallery to the one and two main bearings.

The NTSB's narratives can run to many pages; this is the opening. Read the full report at the NTSB.

About this page

Everything above comes from the NTSB's public accident database and is rewritten in plain English only where the NTSB used codes; the probable cause and narrative are the NTSB's own words. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number CHI00LA209.