NTSB CAROL · Event
Event CHI05LA064
Registry · N1767R
FAA Aircraft Registry record.
Make / Model
CESSNA A185F
Year of manufacture
1974 · 31 years old at event
Engine
CONT MOTOR IO 520 SERIES (285 hp)
Seats / Engines
6 seats · 1 engine
Last airworthiness date
19740910
ADS-B equipped
Yes — Mode-S A132D4
Registrant of record
HAMEL DAVID A
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
A failure of the tail wheel locking mechanism which resulted in the pilot's inability to maintain directional control of the airplane during the landing roll.
Factual narrative
On February 3, 2005, at 1500 central standard time, a Cessna A185F, N1767R, collided with the terrain following a loss of directional control, while landing on runway 36 (4,855 feet by 100 feet, dry asphalt) at the Anoka County-Blaine Airport (ANE), Minneapolis, Minnesota. The private pilot was not injured. The airplane was substantially damaged. The 14 CFR Part 91 personal flight was operating in visual meteorological conditions without a flight plan. The flight originated from the Konshok Airport (PKD), Park Rapids, Minnesota, at 1350. The pilot reported that after touching down he raised the flaps to put more weight on the aircraft wheels. He stated that as the airplane slowed, it began turning to the right. The pilot stated he already had left aileron and rudder applied because there was a slight crosswind. However, he applied more aileron and rudder but the turn became more severe. He stated he tried the left brake to no avail. He stated the airplane was veering about 30 degrees off the runway centerline and he applied right brake to try and slow the airplane. The pilot stated the airplane began to skid as it traveled to the side of the runway at a speed of 35 to 40 knots. The pilot stated the airplane tipped to the left when it contacted the slushy grass. The left wing and left horizontal stabilizer contacted the ground prior to the airplane settling back on the main gear. The pilot stated the airplane continued to turn until it came to rest facing the runway. The pilot stated he purchased the airplane in December 2004, and flew it for the first time during the week prior to the accident. His first flight consisted of five full stop landings with an instructor. He stated that both he and the instructor noted that the airplane was not taxiing right and that the left brake felt "soft." He stated he flew the airplane to ANE and on February 1, 2005, he made six full stop landings in the airplane at ANE. The pilot stated that the airplane was not handling "perfect" during this flight, but that it was "OK." The pilot stated that on the following day he flew the airplane back to PKD with a list of discrepancies that needed to be fixed. He stated the brakes were on the list. He stated that when he landed PKD the left brake was not working and the airplane veered on the runway coming to rest facing the runway edge. The pilot stated that following the maintenance he taxied and test flew the airplane, and the brakes functioned properly. It was on his return flight back to ANE following the maintenance that the accident occurred. Post accident inspection of the airplane was conducted by an inspector from the Federal Aviation Administration Flight Standards District Office in Minneapolis, Minnesota. The inspector reported the tail wheel steering pawl was worn to the point that it would not sufficiently lock the locking collar allowing the tail wheel to castor on landing. The airplane collided with the terrain following a loss of directional control after touchdown. The pilot reported that after touching down, as the airplane slowed, it began turning to the right. The pilot stated he already had left aileron and rudder applied because there was a slight crosswind. However, he applied more aileron and rudder but the turn became more severe. He stated he tried the left brake to no avail. He stated the airplane was veering about 30 degrees off the runway centerline and he applied right brake to try and slow the airplane. The pilot stated the airplane began to skid as it traveled to the side of the runway at a speed of 35 to 40 knots. The pilot stated the airplane tipped to the left when it contacted the slushy grass. The left wing and left horizontal stabilizer contacted the ground prior to the airplane settling back on the main gear. The pilot stated the airplane continued to turn until it came to rest facing the runway. Post accident inspection of the airplane revealed the tail wheel steering pawl was worn to the point that it would not sufficiently lock the locking collar allowing the tail wheel to castor on landing. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_CHI05LA064.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 ↗