NTSB CAROL · Event
Event IAD05LA082
Aircraft involved
Probable cause & findings
The pilot's failure to maintain directional control during landing, which resulted in a collision with a drainage ditch.
Factual narrative
On June 23, 2005, at 1544 eastern daylight time, a Beech C35, N6908, was substantially damaged while landing at the Greenwood Lake Airport (4N1), West Milford, New Jersey. The certificated private pilot and passenger were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight, which originated at the Burlington International Airport (BVT), Burlington, Vermont, and conducted under 14 CFR Part 91. During a telephone interview, the pilot recounted the events that transpired during the landing. Upon arrival at 4N1, he elected to land on runway 24. During the final approach, the pilot maintained about "80 knots" indicated airspeed. He also recalled the winds as being at about 4 to 5 knots. On touchdown, the airplane started "veering to the left," and he felt that the right brake was not working properly. The airplane continued veering to the left, and he remembered that he applied "full" right rudder and aileron, with no effect. The airplane then departed the paved surface of the runway. According to the grounds keeper of the airport, the airplane appeared to touch down "crooked" and not aligned with the runway. The airplane then struck a runway edge light with the right wing, and continued into the airport infield until it hit rocks and a drainpipe. The airplane then "jumped up" 20 to 40 feet in the air, and traveled about 100 feet horizontally until it impacted the ground in a nose down attitude. Examination of the accident site and airplane by a Federal Aviation Administration (FAA) inspector revealed that the airplane came to rest perpendicular to the runway in the airport infield, with its flaps extended approximately 30 degrees. No ground scarring or skid marks were discovered on the runway or infield of the airport; however, measurements taken from the broken runway edge light to where the airplane came to rest, revealed that the airplane had traveled 626 feet after departing the paved surface of the runway. Both wings exhibited impact damage, and compression buckling of the upper left wing skin was evident. All three landing gear legs were damaged. The left main landing gear leg had separated from the airframe and its brake assembly had sheared off. The right main landing gear had remained attached to the airplane, however; the brake bleed valve had been broken off. Examination of the airplane's braking system revealed that the brake fluid reservoir had fluid present on the dipstick and the brake system exhibited no evidence of preimpact damage or malfunction. A review of the airplane's maintenance records showed that the wheel cylinders, flexible lines, toe brake cylinders, and brake linings had been replaced on September 3, 2003. No discrepancies were noted with the brake system after that date. The airplane had operated approximately 53 hours since its most recent annual inspection, which occurred on April 11, 2005, when a functional check of all systems was performed. According to a flight instructor who "checked out" the pilot in the airplane, they flew three or four flights together to meet insurance requirements. He also stated that the airspeed indicator read in miles per hour, and that he taught the pilot to use the airspeeds listed in the Pilot's Operating Handbook and "round them up." The weather reported at the Sussex Airport (FWN), Sussex, New Jersey, located about 14 nautical miles west, at 1553, included variable winds at 5 knots, clear skies below 12,000 feet, temperature 77 degrees Fahrenheit, dewpoint 50 degrees Fahrenheit, and an altimeter setting of 30.12 inches of mercury. According to the pilot, during landing, the airplane veered left, and he felt that the right brake was not working properly because full right rudder and aileron had no effect. A witness who observed the accident stated that the airplane appeared to touchdown "crooked" and not aligned with the runway. The airplane then departed the left side of the runway, struck a runway edge light, and then a drainage ditch before coming to rest another 100 feet further. Examination of the airplane's braking system did not reveal any preimpact malfunctions. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_IAD05LA082.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 (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…
- 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.
- 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.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗