NTSB CAROL · Event
Event WPR12LA261
Registry · N488EA
FAA Aircraft Registry record.
Make / Model
PIPER PA46R-350T
Year of manufacture
2008 · 4 years old at event
Engine
LYCOMING TIO-540-AE2A (350 hp)
Seats / Engines
6 seats · 1 engine
Last airworthiness date
20080229
ADS-B equipped
Yes — Mode-S A606B6
Registrant of record
CHRISTOPHER JASON LEE
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The fatigue failure of the nose landing gear actuator attach foot during the landing roll. Contributing to the accident was the non-compliance with the manufacturer’s service bulletin.
Factual narrative
On June 4, 2012, about 1825 Pacific daylight time, a Piper PA46R-350T, N488EA, experienced a collapse of the nose landing gear at Cameron Airpark, Cameron Park, California. The private pilot, who was the sole occupant, was not injured, but the airplane, which was owned and operated by the pilot, sustained substantial damage. The 14 Code of Federal Regulations Part 91 personal flight, which departed Palo Alto Airport, Palo Alto, California, about 55 minutes prior to the accident, was being operated in visual meteorological conditions. No flight plan had been filed. According to the pilot, he made a normal uneventful landing, but during the landing roll the airplane's nose landing gear collapsed. After the collapse of the nose gear, the airplane temporarily departed the runway and encountered soft terrain, but the pilot was then able to bring it back onto the runway surface before it came to a stop. According to the Federal Aviation Inspector who responded to the scene, a part of the gear actuation and support system had separated from the location where it was attached to the engine mount, allowing the nose gear to partially retract, and resulting in a portion of the actuating system coming in contact with the firewall. The airplane was recovered to an on-field maintenance shop, where it underwent further examination. The examination of the airplane, which was under the direct supervision of a Federal Aviation Administration (FAA) Inspector assigned to the Sacramento Flight Standards District Office, revealed that the right side gear actuator attach foot had fractured and separated from the engine mount. The actuator then moved upward and aft, which allowed the nose landing gear to partially retract. As a result of the forces generated by the partial retraction of the nose landing gear, and the departure of the airplane from the runway, several engine mount braces were found either bent or broken. During this sequence of events, the engine firewall was substantially damaged. A field examination of the fractured metal tube revealed that a majority of the fracture face around its circumference showed a rough granular surface with a 45 degree fracture angle consistent with overload failure. A short section of the fracture, approximately 3/8 inch long, revealed the smoother shiny surface with beach marks and an area of pre-failure oxidation consistent with the propagation of a fatigue crack. A review of the airframe log book indicated that Piper Aircraft Service Bulletin 1103D (SB 1103D), issued on February 2, 2011, concerning the repetitive 100-hour inspection of the engine mount assembly for cracks, was complied with during an Annual Inspection performed on March 15, 2011. At the time of that inspection the airplane had accumulated 617.6 total hours. According to the inspection log entry no defects were found. The aircraft received its next Annual Inspection on March 9, 2012, and according to the log book, at that time the airplane had accumulated 888.3 total hours. The log book entry from that Annual Inspection did not reference any compliance actions associated with SB 1103D, and there were no other subsequent entries referencing compliance with SB 1103D in the airplane’s log book. At the time of the accident, the airplane had accumulated 930 hours total time, and 313 hours since the last time SB 1103D was complied with. The investigation determined that although Piper Aircraft Company considers their Service Bulletins to be mandatory actions, the FAA does not require that they be complied with for aircraft that are used exclusively for FAR Part 91 operations, as this airplane was. Therefore, neither the owner of the airplane or the maintenance shops performing the annual inspections were required to make sure the actions called for by SB 1103D were complied with. However, failure to comply with SB 1103D could create the situation where fatigue cracks that would have been detected during SB 1103D compliance actions might go undetected, and eventually lead to the failure of a component of the engine mount/gear support assembly. During the landing roll after a normal touchdown, the nose landing gear collapsed, and the airplane departed the side of the runway. The investigation determined that the gear collapse was the result of the fatigue failure of the right side nose gear actuator attach foot, which then separated from the engine mount. Records showed that the accident airplane had been flown more than 300 hours since its most recent compliance with the Piper Aircraft service bulletin (SB) 1103D, which calls for the inspection of this specific area for cracks every 100 hours. Although Piper Aircraft Company considers its service bulletins to be mandatory actions, the Federal Aviation Administration does not require that service bulletins be complied with for aircraft that are used exclusively for 14 Code of Federal Regulations Part 91 operations, as this airplane was. Therefore, neither the owner of the airplane nor the maintenance personnel who performed annual inspections on the airplane were required to ensure compliance with SB 1103D. Failure to comply with SB 1103D could result in the nondetection of fatigue cracks that would eventually lead to the failure of a component of the engine mount/gear support assembly, as occurred in this accident. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft systems-Landing gear system-Nose/tail gear attach section-Fatigue/wear/corrosion - C
- C Aircraft-Aircraft systems-Landing gear system-Nose/tail gear attach section-Failure - C
- F Aircraft-Aircraft systems-Landing gear system-Nose/tail gear attach section-Not inspected - F
- — Personnel issues-Task performance-Inspection-Scheduled/routine inspection-Not specified
Verbatim from NTSB's published report. Source file
NTSB_2012_WPR12LA261.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 ↗