NTSB CAROL · Event
Event CHI98LA019
Registry · N33252
FAA Aircraft Registry record.
Make / Model
PIPER J3L-65
Year of manufacture
1940 · 57 years old at event
Engine
CONT MOTOR A&C65 SERIES (65 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
19560105
ADS-B equipped
Yes — Mode-S A3A05F
Registrant of record
AKIN CHRISTOPHER J
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
failure of the normal braking system, due to a low level of brake fluid. Factors relating to the accident were: inadequate inspection of the aircraft by other maintenance personnel, the pilot's failure to check the brakes after brake maintenance/inspection, the tailwind, and the location of trees.
Factual narrative
On October 18, 1997, at 1700 central daylight time, a Piper J3L-65, NC-33252, operated by a private pilot, was substantially damaged when the airplane overran the runway on landing and struck trees at a private airstrip, near Reeseville, Wisconsin. The pilot reported no injuries. Visual meteorological conditions prevailed at the time of the accident. The personal flight was being conducted under 14 CFR Part 91 and no flight plan was on file. The flight departed Hartford Municipal Airport at 1545 cdt. In an interview, the pilot said that at the time of the accident, the winds were from the southwest at 10 knots. He entered the traffic pattern on a left downwind for a northbound landing on his private airstrip. The pilot reported that he landed approximately one-third of the way down the 900' grass strip. During the roll out, he depressed the brake pedals and found both to be ineffective in slowing the airplane. He said that because of trees off the departure end of the runway, a go-around attempt would have been inappropriate. He opted to continue the landing roll, swerving to the left before colliding with trees off the departure end of the runway. Examination of the wreckage by the Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) revealed substantial damage to the right wing, which had separated from the airframe. The right wing leading edge, approximately four feet outboard of the wing root, revealed chordwise crushing. The brakes pedals were depressed and it was confirmed that there was no brake engagement at either wheel. Examination of the brake system by the FAA revealed that upon removal of the main wheels, the brake expander tubes on both wheels were found to be hardened and stiff. Further investigation revealed that the master cylinder reservoir was not full. After adding approximately 1\2 ounce of brake fluid to the reservoir, the brakes engaged. In November 1996, the airplane underwent its most recent annual inspection. An aircraft log entry dated November 19, 1996, indicates that the brake master cylinders were checked and serviced. The pilot said that three flights prior to the accident, on September 13, 1997, the brakes felt 'soft' following a landing at Hartford Airport. At a Fixed Base Operation (FBO) on the field, the pilot asked the maintenance department to check the brakes. He said that the maintenance facility indicated to him that the brakes were tested, no anomalies were found, and that no work had been done to the airplane. There was no entry made in the aircraft logbook reflecting any service work being done. The pilot said that he flew the accident airplane twice after the brakes were tested by the maintenance facility, prior to the accident flight. The pilot stated that he did not recall ever using or testing the brakes at any time during this time. He said that he usually only uses the brakes after landing at Reeseville, due to the short landing area. The pilot said that the winds were from the southwest at 10 knots. He entered the traffic pattern on a left downwind for a northbound landing on his private airstrip. He reported that he landed approximately one-third of the way down the 900' grass strip. During the roll out, he depressed the brake pedals and found both to be ineffective in slowing the airplane. He said that because of trees off the departure end of the runway, a go-around attempt would have been inappropriate. He opted to continue the landing roll, swerving to the left before colliding with trees off the departure end of the runway. Postaccident inspection confirmed that there was no brake engagement at either wheel. Examination of the brake system revealed that the master cylinder reservoir was not full. After adding approximately 1\2 ounce of brake fluid to the cylinder, the brakes engaged. The pilot said that three flights before the accident, the brakes felt 'soft' following a landing. He said that he flew the accident airplane twice after the brakes were tested by a maintenance facility, prior to the accident flight. The pilot stated that he did not recall ever using or testing the brakes at any time during this time. He said that he usually only used the brakes after landing at Reeseville, due to the short landing area. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_CHI98LA019.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗