NTSB CAROL · Event
Event DFW05LA007
Registry · N11FB
FAA Aircraft Registry record.
Make / Model
JOHN P PIKE FLY BABY
Seats / Engines
1 seats · 1 engine
ADS-B equipped
Yes — Mode-S A02A59
Registrant of record
PIKE JOHN P
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The loss of engine power due to the failure of the number one connecting rod. A contributing factor was the lack of suitable terrain for the forced landing.
Factual narrative
On October 16, 2004, at 1315 central daylight time, a Cessna T210N, single-engine airplane, N11FB, was substantially damaged during a forced landing following a reported loss of engine power near Seven Points, Texas. The instrument rated private pilot and passenger were not injured. The airplane was registered to and operated by the pilot. Visual meteorological conditions prevailed and a flight plan was not filed for the 14 Code of Federal Regulations Part 91 personal flight. The cross-country flight originated from Lancaster Airport, near Lancaster, Texas, approximately 1300, and was destined for Athens Municipal Airport, near Athens, Texas. The 3,500-hour pilot reported in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) that during cruise flight at 3,500 feet mean sea level (msl), "the engine lost power." Subsequently, the pilot initiated a forced landing to an open field. During the landing roll, the right horizontal stabilizer struck a bale of hay. Examination of the airplane by an Federal Aviation Administration (FAA) inspector, who responded to the accident site, revealed the outboard leading edge of the right horizontal stabilizer was bent, and the right elevator was partially separated from its mounting attachment. The empennage was bent to the left approximately 10 degrees. A review of the airplane maintenance records revealed the airplane underwent its most recent annual inspection on July 8, 2004, at an aircraft total time of 2,882.5 hours and engine total time of 1,155.3 hours since major overhaul. The Continental TSIO-520-R (9) engine underwent a "top" overhaul on May 18, 2004, at an engine total time of 880.1 hours since major overhaul. At the time of the accident, the aircraft and engine had accumulated 329.8 hours since the top overhaul was performed, at an engine total time of 1,209.9 hours. The engine was examined on November 1, 2004, at the facilities of Air Salvage of Dallas, near Lancaster, Texas, by a representative from Teledyne Continental Motors, under the supervision of the NTSB investigator-in-charge. The examination revealed that the #1 connecting rod was separated from the rod journal into six pieces. The rod cap bearing was oil covered and did not display any signs of heat distress. The cam shaft was separated forward of the #1 cam lobe. The fracture was consistent with overload. The top spark plugs were removed and examined. When compared to the Champion Aviation Check-A-Plug Chart, all spark plugs displayed signatures consistent with normal operation. When rotated by hand, the left and right magneto produced a spark on all leads. The remaining portions of the #1 connecting rod were sent to the Office of Research and Engineering, Materials Laboratory Division in Washington, D.C. for further examination. Examination of the #1 connecting rod by the Office of Research and Engineering, Materials Laboratory Division in Washington, D.C., revealed a fatigue fracture was located where the connecting rod and connecting rod cap attach. The 3,500-hour pilot reported that during cruise flight the engine lost power. Subsequently, the pilot initiated a forced landing to an open field. During the landing roll, the right horizontal stabilizer struck a bale of hay. Examination of the engine revealed that the #1 connecting rod was separated from the rod journal into six pieces. A metallurgical examination of the remaining portions of the #1 connecting rod revealed that a fatigue fracture was found where the connecting rod and connecting rod cap attach. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_DFW05LA007.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 ↗