NTSB CAROL · Event
Event LAX06CA084
Registry · N531HP
FAA Aircraft Registry record.
Make / Model
CESSNA T206H
Year of manufacture
2001 · 5 years old at event
Engine
LYCOMING TI0-540 SER (310 hp)
Seats / Engines
6 seats · 1 engine
Last airworthiness date
20010102
ADS-B equipped
Yes — Mode-S A6B4E1
Registrant of record
FLORIDA HIGHWAY PATROL
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's failure to maintain proper runway alignment, which resulted in a collision with multiple objects.
Factual narrative
On January 8, 2006, about 0015 Pacific standard time, a Cessna T206H, N531HP, collided with multiple airport objects during the landing flare to runway 31 at Palo Alto Airport, Palo Alto, California. The California Highway Patrol (CHP) was operating the public-use airplane under the provisions of 14 CFR Part 91. The commercial pilot and three passengers were not injured; the airplane sustained substantial damage. The cross-country flight departed Santa Maria, California, about 2245. The flight was destined for Palo Alto. Night visual meteorological conditions prevailed, and no flight plan had been filed. In a written statement to the National Transportation Safety Board, the Chief Airplane Pilot for the CHP stated the pilot was landing at the destination airport at the time of the accident. The purpose of the flight was to transport family members of an East Palo Alto police officer who had been killed earlier that day. On approach, the pilot was unable to lower the flaps. He entered the traffic pattern and positioned the airplane for landing on runway 31. He flared for landing, lost sight of the runway, and the airplane drifted to the west side of the runway. The airplane's left elevator, right horizontal stabilizer, rudder, tail cone, and rear bottom fuselage were damaged after colliding with a runway directional sign and two runway edge lights. The pilot believed that he had a flat tire and decided to go-around. He was unable to ascertain the damage to the airplane and elected to divert to San Jose International Airport (SJC), San Jose, California, due to the longer and wider runways. The pilot made a successful no flap landing at SJC. Following the accident, CHP maintenance personnel performed a functional test on the flap system and determined it was operational. In addition, they reported that the right rear passenger side door is equipped with a door/flap limit switch. The switch deactivates the flaps when the door is slightly ajar to fully open, thus preventing the flaps from being lowered. Maintenance personnel determined that the right rear passenger was leaning "heavily" against the door and deactivated the door/flap limit switch, which prevented the flaps from lowering. The CHP stated there were no mechanical malfunctions or failures with the airplane prior to the accident. The airplane collided with multiple airport objects during the landing flare. While in the traffic pattern for landing the pilot was not able to lower the flaps. During the landing flare, the pilot lost sight of the runway, and allowed the airplane to drift off the runway, where it collided with an airport sign and runway lights. He performed a go-around, and was not able to determine the extent of the damage. He elected to divert to another area airport with longer and wider runways. The pilot made a no flap landing at the alternate airport. Maintenance personnel reported that the right rear passenger door has a door/flap limit switch, so that when the door is ajar or open, the flaps cannot be lowered. The system was functionally tested and found to operate normally. It was determined that the right rear passenger was leaning against the door, and deactivated the door/flap limit switch. No further discrepancies were noted. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2006_LAX06CA084.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 ↗