# NTSB LAX02FA163: Cessna T210M, N761LX, Groveland, CA, May 13, 2002 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: May 13, 2002, 13:55 local (20:55 UTC) - Place: Groveland, CA - Coordinates: 37.839168, -119.858055 - Nearby events: https://openairdocs.org/map.md?lat=37.8392&lon=-119.8581&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 2 fatal - Status: Completed, report March 28, 2006 - Report: Approved by Office Director - Parties: Federal Aviation Administration, Teledyne Continental Motors Inc., Cessna Aircraft Company - NTSB case key (mKey): 54704 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX02FA163 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54704/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54704 - Page: https://openairdocs.org/ntsb/LAX02FA163 ## Probable cause a catastrophic engine failure due to the fatigue fracture and failure of the crankshaft. A factor contributing to the accident was the unsuitable nature of the mountainous terrain for a successful forced landing. The precipitating cause of the fatigue fracture could not be determined. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power(total) - mech failure/malf, cruise - engine assembly,crankshaft - fatigue (cause) - engine assembly,crankshaft - fractured (cause) - Forced landing, emergency descent/landing - emergency procedure - attempted, pilot in command - In flight collision with object, emergency descent/landing - terrain condition - mountainous/hilly - object - tree(s) - terrain condition - none suitable (contributing factor) ## Analysis The airplane collided with multiple trees during an attempted forced landing in mountainous terrain following a catastrophic engine failure in cruise. The flight was obtaining VFR flight following from air route traffic control center (ARTCC) when the facility lost radar and radio contact. The airplane came to rest near the edge of an elliptical meadow, which was about 1 mile long by 1/4 mile wide, with the long axis oriented east and west. The meadow was in mountainous terrain and surrounded by trees over 100 feet tall. The debris path was along the eastern edge of the meadow on a magnetic bearing of 210 degrees. Multiple large trees were observed with broken branches and major impact marks on their trunks. The crankcase had a 3-inch diameter hole in it above cylinder number 3. Examination of the engine found that the crankshaft fractured and separated at the rear of the number 4 cheek. The fracture was at the forward radius of the number 2 main bearing journal. Smeared metal was on the fracture surfaces. A metallurgical examination determined that a large portion of the fracture surface exhibited smooth crack arrest markings typical of fatigue propagation. Failure of the crankshaft was caused by a fatigue crack in the cheek between the number 3 rod journal and the number 2 main bearing journal. The fracture of the crankshaft caused the additional damage to the engine, including the separation of the numbers 3 and 4 connecting rods from their respective journals, and would have led to a complete loss of engine power. The origin of the fatigue fracture was in the transition between the number 2 main bearing journal surface and the forward fillet radius, approximately 0.036 inches below the surface of the journal. No metallurgical anomalies or manufacturing process errors were found to explain the fatigue initiation. This failure is very similar to a number of others investigated by the Safety Board's Materials Laboratory in the past, with a fatigue crack initiating just below the hardened case layer. As with many of those previous events, there were no material or microstructural defects that could be identified as the root cause of the fatigue initiation. The crankshaft met design material specifications. ## Factual narrative HISTORY OF FLIGHT On May 13, 2002, at 1355 Pacific daylight time, a Cessna T210M, N761LX, collided with trees during a forced landing in mountainous terrain near Groveland, California. The forced landing was precipitated by a catastrophic engine failure in cruise. The owner was operating the airplane under the provisions of 14 CFR Part 91. The airline transport pilot and one passenger sustained fatal injuries. The airplane was destroyed by the collision sequence and post crash fire. The personal cross-country flight departed Fullerton, California, about 1130, en route to the airplane's home base in Carson City, Nevada. Visual meteorological conditions prevailed, and no flight plan had been filed. The primary wreckage was at 37 degrees 50.358 minutes north latitude and 119 degrees 51.484 minutes west longitude at an estimated elevation of 4,595 feet. The airplane became the subject of an alert notice (ALNOT) when Oakland (ZOA) Air Route Traffic Control Center (ARTCC) lost radar and radio contact at 1356. ZOA lost contact 50 miles northeast of Linden, California, at 12,500 feet. Local authorities responded about 1430 to a report of a fire, and discovered the airplane's wreckage. The National Transportation Safety Board investigator-in-charge (IIC) reviewed recorded radio transmissions by the pilot and air traffic control. The IIC converted all times to Pacific daylight time. The pilot contacted Oakland Center at 1311, and reported level at 12,500 feet en route to Carson City. The pilot made a couple of frequency changes as the airplane changed radar sectors. At 1354, the pilot reported level at 12,500 feet, and several transmission exchanges followed. The last transmission was at 1355:16. The pilot verified that he was proceeding to Carson City via Placerville, California, and then would cut across the Sierra Mountains near Lake Tahoe, California. At 1356:35, the controller tried to inform the pilot that he had lost radar contact, but received no reply. After several attempts, the controller asked an airliner in the vicinity to try and contact the pilot; there was no response. A review of a plot of recorded radar data provided by the airframe manufacturer showed a target that departed Fullerton at 1217:41. The target proceeded in a northerly direction, and climbed to a mode C reported altitude of 12,500 feet. It reached 12,500 feet near Palmdale, California. The target maintained that altitude on a relatively straight track. The last target was at 1355:21, at a mode C altitude of 12,500 feet. The coordinates were 37 degrees 51 minutes 15 seconds north latitude and 119 degrees 49 minutes 10 seconds west longitude. The plot showed a primary target at 1355:40, at 37 degrees 52 minutes 01 seconds north latitude and 119 degrees 49 minutes 09 seconds west longitude. PERSONNEL INFORMATION A review of Federal Aviation Administration (FAA) airman records revealed that the pilot held an airline transport pilot certificate with an airplane multiengine land rating, and a commercial pilot certificate with an airplane single engine land rating. The pilot held a second-class medical certificate issued on April 30, 2001; it had no limitations or waivers. The Safety Board IIC was unable to locate personal flight records for the pilot. The IIC obtained the aeronautical experience listed in this report from a review of the FAA airmen medical records on file in the Airman and Medical Records Center located in Oklahoma City, Oklahoma. The pilot reported on his medical application that he had a total time of 7,200 hours with 300 hours logged in the last 6 months. AIRCRAFT INFORMATION The airplane was a Cessna T210M, serial number 21062351. A maintenance shop had recently completed a pitot/static transponder check on the airplane. They routinely placed the logbooks in the airplane following any work. The owner could not find the logbooks, and assumed that they were still in the airplane. The owner stated that he owned the airplane for 12 to 14 years. When he purchased the airplane, it had 710 hours on it. Shortly after his purchase, he had one or two cylinders top overhauled. His company flew the airplane about 500 hours before they had camshaft problems and overhauled the engine. Therefore, he estimated that the airframe and engine had about 1,200 hours at the time of engine overhaul. He had work done on one or two cylinders about 200 hours prior to the accident. He estimated that the airframe had about 1,920 hours total time. The maintenance shop provided work orders for the airframe. The shop completed an annual inspection on July 16, 2001. Total time on the airframe was 1,841 hours. The last work order indicated that they removed and sent the transponder and encoding altimeter to other shops for bench testing. Upon the units' return, the shop installed them in the airplane and completed a pitot/static and transponder test. On April 18, 2002, they noted a total time of 1,897 hours. The engine was a Teledyne Continental Motors TSIO-520R, serial number 512516. METEOROLOGICAL INFORMATION A routine aviation weather report (METAR) for Modesto, California (240 degrees at 55 miles), was issued at 1353. It stated: skies clear; visibility 10 miles; winds from 330 degrees at 13 knots; temperature 81 degrees Fahrenheit; dew point 31 degrees Fahrenheit; altimeter 30.06 inches of mercury. COMMUNICATIONS The airplane had established radio contact with Oakland Center, and was on frequency 126.85. WRECKAGE AND IMPACT INFORMATION The Safety Board IIC and representatives from the FAA, Cessna Aircraft Company, and Teledyne Continental Motors (TCM) examined the wreckage on scene. The airplane came to rest near the edge of an elliptical meadow, which was about 1 mile long by 1/4 mile wide, with the long axis oriented east and west. The meadow was in mountainous terrain and surrounded by trees over 100 feet tall. The debris path was along the eastern edge of the meadow on a magnetic bearing of 210 degrees. The airplane came to rest about 245 feet from the first identified point of contact (FIPC), which was a 4-inch diameter tree with the trunk broken about 10 feet above the ground. All measurements in this section are looking from the FIPC along the debris path centerline and left or right of the centerline. The coordinates for the FIPC were 37 degrees 50.388 minutes north latitude and 119 degrees 51.449 minutes west longitude at an estimated altitude of 4,550 feet. Ten feet right of the FIPC was a 15-foot-tall tree that did not have any scrape marks or broken branches. Thirty-six feet from the FIPC and 14 feet left, was a 100-foot-tall tree with scarred branches about 30 feet up from its base. At 144 feet and 14 feet left, was another 100-foot-tall tree with a 2-foot diameter trunk. About 25 feet up the trunk was a round 2-foot scarred area that had no bark covering about 20 percent of the tree's circumference. Thirty-two feet left of this tree was a piece of aluminum skin whose fracture surfaces mated to the fracture surfaces of the left wing. The inverted left wing, which separated, was 177 feet from the FIPC on the centerline of the debris path. The left wing exhibited cylindrical crush damage that was about 2 feet in diameter. A piece of red lens remained in its fitting on the left wing tip, and shards of red lens were within 10 feet of the wing. The tree line began about 190 feet from the FIPC. Numerous trees in the debris path had broken limbs from 5 to 10 feet above ground level. One flap section, which was about a foot long, was at 204 feet and 10 feet left, and another similar sized piece was at 213 feet and 3 feet left. The left wing and pieces of the airplane that were not in burned areas were not oily, sooty, or scorched. Several Plexiglas shards that the airplane manufacturer's representative identified as windscreen components lay outside of the b ## Aircraft - Registration: [N761LX](https://openairdocs.org/deregistered/N761LX-2002-09-04), registration cancelled 2002-09-04, S/N 21062351, built 1977 (OpenAirDocs) - Reported make and model: Cessna T210M - Registry model: [Cessna T210M](https://openairdocs.org/model/cessna-t210m) (registry code 2073451) (OpenAirDocs) - Registry engine: [Continental TSIO-520 series](https://openairdocs.org/engine/continental-tsio-520-series) (registry code 17040, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 21062351 - Airframe hours: 1920 - Engines: Continental TSIO-520R 300 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Registered owner: R. P. Weddell & Sons - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 1, 2001, 23 hours before - Departed: FUL, FULLERTON, CA - Destination: CXP, CARSON CITY, NV ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 45; injuries: fatal; flight instructor, airline transport, commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--no waivers/lim.; seat: left; flight hours: 7,200 total ## Weather - Conditions: Visual (VMC), Day - Wind: 330° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 81 °F, dew point 30 °F - Altimeter: 30.05 inHg - Observed at: MOD, 55 nm away ## 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 20020513010589A](https://openairdocs.org/incident/20020513010589A), May 13, 2002: Cessna T210M, Groveland, CA, No damage, 2 fatal. (-23) On may 13, 2002, about 1359 pacific daylight time, a Cessna T210M, N761LX, collided with trees near Groveland, California. The owner was operating the… ## Docket (26 files) The files NTSB released with the investigation on December 31, 2005, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54704. 66.5 MB in all. - Materials Laboratory Factual Report 02-115, Crankshaft section (item 1, .PDF, 4 photos, 5.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40172837&FileExtension=.PDF&FileName=Materials%20Laboratory%20Factual%20Report%2002-115,%20Crankshaft%20section-Master.PDF - Wreckage Diagrams (item 2, .PDF, 17 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242533&FileExtension=.PDF&FileName=Wreckage%20Diagrams-Master.PDF - Transcript of Radio Communications (item 3, .PDF, 172 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242536&FileExtension=.PDF&FileName=Transcript%20of%20Radio%20Communications-Redacted.PDF - Photo 1-Accident Site Area (item 4, .PDF, 185 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242539&FileExtension=.PDF&FileName=Photo%201-Accident%20Site%20Area-Master.PDF - Photo 2-First Identified Point of Contact (item 5, .PDF, 205 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242540&FileExtension=.PDF&FileName=Photo%202-First%20Identified%20Point%20of%20Contact-Master.PDF - Photo 3-Left Wing and Tree (item 6, .PDF, 206 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242543&FileExtension=.PDF&FileName=Photo%203-Left%20Wing%20and%20Tree-Master.PDF - Photo 4-Left Wing (item 7, .PDF, 195 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242546&FileExtension=.PDF&FileName=Photo%204-Left%20Wing-Master.PDF - Photo 5-Main Wreckage Looking Back in Direction of Flight (item 8, .PDF, 195 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242548&FileExtension=.PDF&FileName=Photo%205-Main%20Wreckage%20Looking%20Back%20in%20Direction%20of%20Flight-Master.PDF - Photo 6-Main Wreckage (item 9, .PDF, 172 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242551&FileExtension=.PDF&FileName=Photo%206-Main%20Wreckage-Master.PDF - Photo 7-Right Side of Main Wreckage (item 10, .PDF, 204 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242553&FileExtension=.PDF&FileName=Photo%207-Right%20Side%20of%20Main%20Wreckage-Master.PDF - Photo 8-Top of Engine & Prop (item 11, .PDF, 196 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242554&FileExtension=.PDF&FileName=Photo%208-Top%20of%20Engine%20%26%20Prop-Master.PDF - Photo 9-Propeller (item 12, .PDF, 189 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242573&FileExtension=.PDF&FileName=Photo%209-Propeller-Master.PDF - Cessna Radar Plot (item 13, .PDF, 115 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242555&FileExtension=.PDF&FileName=Cessna%20Radar%20Plot-Master.PDF - Cessna Rep Statement (item 14, .PDF, 80 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242556&FileExtension=.PDF&FileName=Cessna%20Rep%20Statement-Master.PDF - TCM Exam 1-13 (item 15, .PDF, 10 photos, 7.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40438413&FileExtension=.PDF&FileName=TCM%20Exam%201-13-Redacted.PDF - TCM Exam 14-21 (item 16, .PDF, 16 photos, 15.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242560&FileExtension=.PDF&FileName=TCM%20Exam%2014-21-Master.PDF - TCM Exam 22-29 (item 17, .PDF, 16 photos, 15.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242561&FileExtension=.PDF&FileName=TCM%20Exam%2022-29-Master.PDF - TCM Exam 30-39 (item 18, .PDF, 20 photos, 19.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242562&FileExtension=.PDF&FileName=TCM%20Exam%2030-39-Master.PDF - NTSB Memo on TCM Engine Exam (item 19, .PDF, 60 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242564&FileExtension=.PDF&FileName=NTSB%20Memo%20on%20TCM%20Engine%20Exam-Redacted.PDF - Maintenance Invoices (item 20, .PDF, 184 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40438414&FileExtension=.PDF&FileName=Maintenance%20Invoices-Redacted.PDF - NTAP Data (item 21, .PDF, 531 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242563&FileExtension=.PDF&FileName=NTAP%20Data-Master.PDF - Record of Conversation-Owner (item 22, .PDF, 44 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242566&FileExtension=.PDF&FileName=Record%20of%20Conversation-Owner-Master.PDF - Record of Conversation-Pilot's Father (item 23, .PDF, 22 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242567&FileExtension=.PDF&FileName=Record%20of%20Conversation-Pilot%27s%20Father-Master.PDF - Pilot Operating Handbook Excerpts (item 24, .PDF, 94 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242568&FileExtension=.PDF&FileName=Pilot%20Operating%20Handbook%20Excerpts-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 25, .PDF, 179 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40242569&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 26, .PDF, 70 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40438415&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.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.