Piper PA-18 accident near Fairbanks, Alaska, August 21, 1998
On August 21, 1998 at about 11:00 pm local time, a Piper PA-18, registered N74996, was substantially damaged in an accident near Fairbanks, Alaska. It was a public-use flight under public-use (government) rules. No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's inadequate preflight planning/preparation, and his delay in aborting the takeoff. Factors in the accident were a short runway area for takeoff, trees located at the end of the runway, and the pilot's excessive application of brakes.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 21, 1998 · about 11:00 pm local time
- Place
- Fairbanks, Alaska · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-18 · all PA-18s on the register
- Registration
- N74996 · registry record · serial 18-75-09112
- Damage
- Substantial damage
- Flight
- Public-use flight · public-use (government) rules
The NTSB's narrative final · quoted from the NTSB record
The certificated commercial pilot was conducting a public use flight in a remote area to inspect a small airstrip used by hunters. The airstrip was oriented north/south, and was about 650 feet long. During a landing at the airstrip, the pilot said the wind was from the south about 18 knots. After inspecting the airstrip, the pilot prepared to depart toward the south. The pilot reported that several trees, about 20 feet tall, were located at the south end of the airstrip. The pilot began a takeoff, and about halfway down the airstrip, he lowered the flaps. The airplane momentarily became airborne, but the pilot said he recognized the airplane was not going to clear the trees. He then raised the flaps, and applied heavy braking when the airplane again touched down. The airplane nosed over at the end of the airstrip. The airplane received damage to the propeller, tail assembly, and the fuselage.
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; single-engine sea; instrument: airplane
- Flight time: 1,266 hours in all; 480 in this make and model; 79 in the last 90 days; 31 in the last 30 days; 1,195 as pilot in command
- Medical certificate: Class 2 (valid medical--no waivers/lim.)
- Seat: frt
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 1,750 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-320-A2B (piston); 0 hours total
The flight
- Departed from: FAI at 6:00 pm
- Runway 18, 650 ft
Weather at the time
- Light: daylight
- Wind: from 180° at 18 knots
- Visibility: 60 statute miles
- Sky: overcast at 7,000 ft; not recorded
- Temperature: 50°F (10°C), dew point 0°F (-18°C)
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.
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.
