# NTSB GAA18CA271: Cessna P210, N210BG, Grass Valley, CA, May 9, 2018 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: May 9, 2018, 11:15 local (18:15 UTC) - Place: Grass Valley, CA - Coordinates: 39.223056, -121.005279 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.2231&lon=-121.0053&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report October 24, 2018 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 97228 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA271 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/97228/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=97228 - Page: https://openairdocs.org/ntsb/GAA18CA271 ## Probable cause The pilot’s improper landing flare, which resulted in a long landing and a runway excursion. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna P210N, 4 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2073454), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna P210N, 18 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2073454), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Terrain: sloped/uneven terrain](https://openairdocs.org/ntsb-findings/03021017): Environmental issues › Physical environment · Response/compensation; cases with it: [Cessna P210N, 1 case](https://openairdocs.org/ntsb-findings/03021017/cases.md?model=2073454), [All aircraft, 270 cases](https://openairdocs.org/ntsb-findings/03021017/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Cessna P210N, 2 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=2073454), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna P210N, 7 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2073454), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna P210N, 12 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2073454), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The pilot reported that, while en route, he noticed a loose camlock screw on the engine cowling and decided to land the airplane at the nearest airport. He added that, during the landing, he applied the brakes, but they had "minimal effect." As the airplane slowed "very slightly," he determined he could make the taxiway turn. But, he added that, "the left steering did not [a]ffect direction." The airplane exited the runway and went over the runway embankment. The airplane sustained substantial damage to the left wing. The pilot reported that the brakes failed to slow the airplane to a complete stop, and the nosewheel failed to turn. A local mechanic examined the brakes following the accident and found no anomalies. The airport manager reported that marks on the runway showed that the airplane had touched down about 1,000 to 1,500 ft beyond the approach end of the runway. Additionally, there was about a 15- ft-long skid mark showing a skidding left turn before the airplane exited the runway. Pictures submitted by the Federal Aviation Administration inspector showed the skid marks turning left while exiting the end of the runway. The airport supplement stated that runway 25 sloped downhill to the west. ## Factual narrative The pilot reported that, while enroute, he noticed a loose camlock screw on the engine cowling and decided to land the airplane at the nearest airport. He added that, during the landing, he applied the brakes, but they had "minimal effect". As the airplane slowed "very slightly", he determined he could make the taxiway turn. But, he added that, "the left steering did not effect direction", the airplane exited the runway, and went over the runway embankment. The airplane sustained substantial damage to the left wing. The pilot reported that the brakes failed to slow the airplane to a complete stop, and the nose wheel failed to turn. A local mechanic inspected the brakes following the accident and found no anomalies. The airport manager reported that, marks on the runway showed the airplane touched down approximately 1000 to 1500 ft beyond the approach end of the runway. Additionally, there was approximately a 150 ft. long skid mark showing a skidding left turn before the airplane exited the runway. Pictures submitted by the Federal Aviation Administration inspector showed the skid marks turning left while exiting the end of the runway. The airport supplement states, runway 25 slopes downhill to west. ## Aircraft - Registration: [N210BG](https://openairdocs.org/aircraft/N210BG), registered now, S/N P21000025, built 1978 (OpenAirDocs) - Reported make and model: CESSNA P210 (N) - Registry model: [Cessna P210N](https://openairdocs.org/model/cessna-p210n) (registry code 2073454) (OpenAirDocs) - Registry engine: [Continental TSIO-520 series](https://openairdocs.org/engine/continental-tsio-520-series) (registry code 17040, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: P21000025 - Year built: 1978 - Airframe hours: 3482 - Engines: CONT MOTOR TSIO-520-P 310 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 3, 2018 - Departed: O02, Beckwourth, CA - Destination: GOO, Grass Valley, CA - Airport: GOO, Nevada County, runway 25, 4,657 × 75 ft, asphalt - Equipment: Stall warning system, Handheld GPS, Electronic multifunction display, Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 68; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review October 17, 2017; seat: left; restraint: 3-point; flight hours: 1,460 total, 460 in this make and model, 1,460 as pilot in command, 6.4 in the last 90 days, 0.8 in the last 30 days, 0.8 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 180° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 48 °F - Altimeter: 30.05 inHg - Observed at: KGOO ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20180509016949A](https://openairdocs.org/incident/20180509016949A), May 9, 2018: Cessna P210N, Grass Valley, CA, Substantial damage. On may 9, 2018 at approximately 1400 hours, N210BG, a Cessna 210 aircraft, was en route from nervino/beckwourth (A02) to visalia municipal airport (vis).… ## Other investigations on N210BG (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB FTW97LA064](https://openairdocs.org/ntsb/FTW97LA064), Dec 18, 1996: Cessna P210N (N210BG), Muskogee, OK, substantial damage. Probable cause: the pilot's improper planning/decision and inaccurate fuel consumption calculations, which resulted in an inadequate supply of fuel, fuel exhaustion, and a subsequent forced landing at night.… ## Docket (4 files) The files NTSB released with the investigation on August 1, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=97228. 27.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 24.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465559&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Mechanic Statement (item 2, .PDF, 32 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465560&FileExtension=.PDF&FileName=Mechanic%20Statement-Master.PDF - Record of Conversation - Airport Manager (item 3, .PDF, 104 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465561&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Airport%20Manager-Master.PDF - Accident Pictures (item 4, .PDF, 4 photos, 2.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40465562&FileExtension=.PDF&FileName=Accident%20Pictures-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.