# NTSB LAX02FA179: Cessna 182P, N52404, Pleasanton, CA, May 28, 2002 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: May 27, 2002, 22:30 local (May 28, 2002, 05:30 UTC) - Place: Pleasanton, CA - Coordinates: 37.635276, -121.931114 - Nearby events: https://openairdocs.org/map.md?lat=37.6353&lon=-121.9311&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed, report September 30, 2003 - Report: Approved by Office Director - Parties: Teledyne Continental Motors, Federal Aviation Administration, Cessna Aircraft Company - NTSB case key (mKey): 54845 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX02FA179 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54845/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54845 - Page: https://openairdocs.org/ntsb/LAX02FA179 ## Probable cause The pilot's inadvertent flight into adverse weather and his failure to maintain clearance. Contributing factors included the pilot's inadequate preflight planning, the low ceilings, and the dark night conditions. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight encounter with weather, maneuvering - preflight planning/preparation - inadequate, pilot in command (contributing factor) - flight into adverse weather - inadvertent, pilot in command (cause) - weather condition - low ceiling (contributing factor) - light condition - dark night (contributing factor) - In flight collision with object, maneuvering - altitude/clearance - not maintained, pilot in command (cause) - object - tree(s) ## Analysis At 2219 the pilot contacted approach control stating that he was at 4,500 feet mean sea level over Mt. Diablo. The controller instructed the pilot to cross the east bay shoreline at or above 2,000 feet mean sea level and remain clear of Class B airspace. At 2228 the controller radioed that he had lost contact with the aircraft. There was no reply from the pilot. The aircraft wreckage was located the next morning at the 1,680-foot level of the mountain range. Impact signatures and wreckage distribution indicated the aircraft impacted trees flying almost parallel to a ridgeline with a wings and nose level attitude. The Area Forecast indicated that by 2200 there would be overcast clouds from 1,000 to 1,500 feet above ground level, with light rain showers and visibility between 3 and 5 statute miles. At 2153, approximately 37 minutes prior to the accident, and at 2253, approximately 23 minutes after the accident, a weather reporting facility located 14.9 nautical miles west of the accident site reported overcast clouds at 700 feet. At 2154, a weather reporting facility located 10 nautical miles west-southwest of the accident site reported overcast clouds at 900 feet; at 2254, it reported overcast clouds at 700 feet. Based on the weather conditions, the mountain ridge where the accident occurred was likely to have been obscured by clouds. A friend of the pilot, who witnessed his departure, reported the pilot did not obtain a weather briefing before takeoff. No aircraft or engine anomalies were noted that would have prevented normal operations. ## Factual narrative HISTORY OF FLIGHT On May 27, 2002, approximately 2230 Pacific daylight time, a Cessna 182P single-engine airplane, N52404, was destroyed when it impacted mountainous terrain while maneuvering near Pleasanton, California. The airplane was registered to and operated by the pilot. The non-instrument rated private pilot, sole occupant of the airplane, sustained fatal injuries. Night instrument meteorological conditions prevailed, and no flight plan was filed for the 14 CFR Part 91 personal cross-country flight. The flight originated at the Nevada Country Air Park Airport, Grass Valley, California, at 2125, and was destined for the San Carlos Airport, San Carlos, California. It was reported to the National Transportation Safety Board investigator-in-charge (NTSB IIC) by a friend of the pilot, whom the pilot had flown from San Carlos to Grass Valley earlier in the evening, that prior to departing on the return trip to San Carlos the pilot added 15 gallons of fuel to both the left and right wing tanks of the airplane. The friend of the pilot also reported that during the flight to Grass Valley, the pilot could hear air traffic control when they transmitted to him, but observed that at times air traffic control could not hear the pilot when he attempted to reply. The pilot's friend also stated that prior to his departure from Grass Valley the pilot did not receive a weather briefing. According to the pilot's brother, who was interviewed by the NTSB IIC, the pilot would frequently fly down the eastern side of the Diablo Mountain range until he was clear of the restricted airspace," then cut across the range and head west directly toward San Carlos." The pilot's brother further stated that this was a regular route the pilot flew and that he was very familiar with the area and the mountainous terrain. He also stated that when he flew with him, his brother "frequently had a hard time holding his altitude." The pilot contacted Sacramento Terminal Radar Approach Control (TRACON) at 2128 and requested flight following to San Carlos at an altitude of 4,500 feet mean sea level. The controller queried the pilot as to his position, and the pilot replied, "Just left, uh, Nevada County." The controller then gave the pilot a transponder code. At 2204 the pilot was instructed to contact Travis Approach Control, which he did. At 2218 the controller instructed the pilot to remain on his current transponder code and to contact Bay Approach. At 2219 the pilot contacted Bay Approach, informing the controller that he was VFR (visual flight rules) to San Carlos, flying over Mount Diablo (elevation 3,849 feet mean sea level) at 4,500 feet mean sea level. The controller instructed the pilot to cross the east bay shoreline at or above 2,000 feet mean sea level and to remain clear of the Class B airspace. At 2228 the controller radioed that he had lost contact with the aircraft, radar services were terminated and that the pilot should change radio frequencies and transponder codes. There was no reply from the pilot. The controller then asked an airline crew flying through the area to try contacting N52404. All attempts to contact N52404 were unsuccessful. Radar data showed the aircraft at an altitude of 4,400 feet mean sea level at 2219:33. The aircraft then climbed slightly, after which it began a descent. At 2223:38 the aircraft's altitude was reported at 2,300 feet mean sea level and radar contact was lost. At 2225:10 the aircraft reappeared on radar at 2,200 feet mean sea level. The aircraft continued descending and reached an altitude of 2,000 feet mean sea level at 2226:01. The aircraft's radar track followed a 195-degree heading and the aircraft maintained an altitude of 2,000 feet mean sea level. At 2227:43, the last radar contact showed N52404 was level at 2,000 feet mean sea level on a heading of 174 degrees 1.1 nautical miles north of the accident site. At 2228, radar contact with N52404 was lost, and all subsequent attempts by the controller to contact the pilot were unsuccessful. The aircraft wreckage was located at 1127 on May 28, at the 1,680-foot level of a 1,930-foot Diablo Mountain Range ridge line, 14.9 nautical miles from the Oakland VOR on the 094-degree radial. PERSONNEL INFORMATIION At the time of the accident the pilot held a private pilot certificate with a rating for single-engine land aircraft. A relative reported that the pilot had accumulated approximately 500 hours of total flight time. The pilot held an expired class III medical certificate dated April 25, 2000. A limitation indicated that the holder must have available glasses for near vision. METEOROLOGICAL INFORMATION The Area Forecast, which covered California, was issued at 1945 on May 27, valid until 0800 on May 28. The forecast for the coastal stations north of Salinas, California, located 64 nautical miles south-southwest of the accident site indicated scattered to broken clouds at 1,500 feet above ground level, broken clouds from 8,000 feet to 10,000 feet above ground level, with isolated light rain showers. By 2200 conditions were forecast to become overcast clouds at 1,000 to 1,500 feet above ground level, layered clouds to 15,000 feet above ground level, with isolated light rain showers and occasional visibility between 3 and 5 statute miles with mist. Airmet Sierra, for IFR (instrument flight rules) and mountain obscuration was issued at 1845 on May 27, valid until 0100 on May 28, covering the accident area. The Airmet specified mountains occasionally obscured by clouds, with conditions continuing beyond 0100 on May 28. Terminal Aerodrome Forecasts (TAF) for Oakland (OAK, located 14.9 nautical miles west of the accident site) and San Jose (SJC, located 15 nautical miles south of the accident site) were issued at 1631 on May 27, and were valid from 1700 on May 27 to 1700 on May 28. The OAK TAF indicated temporary conditions from 2100 May 27 to 0100 May 28 to be visibility 4 statute miles, light drizzle and mist, and overcast clouds at 900 feet above ground level. The SJC TAF indicated from 2200 on May 27 visibility would be greater than 6 statute miles, scattered clouds at 3,500 feet above ground level, and broken clouds at 6,000 feet above ground level. At 2153, the weather observation facility at OAK reported wind 270 degrees at 7 knots, visibility 10 statute miles, overcast clouds at 700 feet, temperature 14 degrees C, dew point 14 degrees C, and an altimeter setting of 30.03 inches of Mercury. At 2253, the weather facility at OAK reported wind 280 degrees at 8 knots, visibility 10 statute miles, overcast clouds at 700 feet, temperature 14 degrees C, dew point 13 degrees C, and an altimeter setting of 30.05 inches of Mercury. At 2154, the weather observation facility at Hayward Municipal Airport (HWD), Hayward, California, (located 10 nautical miles west-southwest of the accident site) reported wind 300 degrees at 7 knots, visibility 10 statute miles, overcast clouds at 900 feet, temperature 14 degrees C, dew point 12 degrees C, and an altimeter of 30.03 inches of Mercury. At 2254, the HWD weather reporting facility indicated wind 300 degrees at 6 knots, visibility 10 statute miles, overcast clouds at 700 feet, temperature 14 degrees C, dew point 12 degrees C, and an altimeter of 30.03 inches of Mercury. At 2153, the weather observation facility located at the Livermore Municipal Airport (LVK), Livermore, California, (located 6 nautical miles northwest of the accident site) reported wind 270 degrees at 5 knots, visibility 10 statute miles, sky clear, temperature 13 degrees C, dew point 12 degrees C, and an altimeter of 30.02 inches of Mercury. At 2253, the weather facility at LVK reported wind 260 degrees at 7 knots, visibility 10 statute miles, broken clouds at 900 feet, broken clouds at 11,000 feet, temperature 13 degrees C, dew point 12 degrees C, and an altimeter of 30 ## Aircraft - Registration: [N52404](https://openairdocs.org/deregistered/N52404-2002-08-30), registration cancelled 2002-08-30, S/N 18262582, built 1973 (OpenAirDocs) - Reported make and model: Cessna 182P - Registry model: [Cessna 182P](https://openairdocs.org/model/cessna-182p) (registry code 2075816) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18262582 - Airframe hours: 3347.6 - Engines: Continental O-470-S 230 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Registered owner: Thomas F. Conlin - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 19, 2002 - Departed: 017, Grass Valley, CA - Destination: SQL, San Carlos, CA ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 51; injuries: fatal; private; airplane ratings: single-engine land; medical: class 3, invalid medical for flight; seat: left; toxicology performed; flight hours: 500 total ## Weather - Conditions: Visual (VMC), Night/dark - Wind: 270° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 55 °F, dew point 54 °F - Altimeter: 30.02 inHg - Observed at: LVK, 6 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 20020527016309A](https://openairdocs.org/incident/20020527016309A), May 27, 2002: Cessna 182P, Alameda, CA, No damage, 1 fatal. (-23) On may 27, 2002, at approximately 2230 pacific daylight time, the aircraft impacted terrain while maneuvering near pleasenton, CA. The aircraft was… ## Docket (20 files) The files NTSB released with the investigation on July 17, 2003, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54845. 11.3 MB in all. - Meteorology 5 - Factual Report of Group Chairman (item 1, .PDF, 7.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40166405&FileExtension=.PDF&FileName=Meteorology%205%20-%20Factual%20Report%20of%20Group%20Chairman-Master.PDF - Witness Statements (item 2, .PDF, 57 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442104&FileExtension=.PDF&FileName=Witness%20Statements-Redacted.PDF - Maps and Wreckage Diagram (item 3, .PDF, 751 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40185262&FileExtension=.PDF&FileName=Maps%20and%20Wreckage%20Diagram-Master.PDF - Weather Reports (item 4, .PDF, 60 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40185251&FileExtension=.PDF&FileName=Weather%20Reports-Master.PDF - Transcript of Radio Communications (item 5, .PDF, 76 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442106&FileExtension=.PDF&FileName=Transcript%20of%20Radio%20Communications-Redacted.PDF - Reports from Parties to the Investigation: Cessna (item 6, .PDF, 101 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40185253&FileExtension=.PDF&FileName=Reports%20from%20Parties%20to%20the%20Investigation%3A%20Cessna-Master.PDF - Reports from Parties to the Investigation: Teledyne Continental Motors (item 7, .PDF, 64 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442110&FileExtension=.PDF&FileName=Reports%20from%20Parties%20to%20the%20Investigation%3A%20Teledyne%20Continental%20Motors-Redacted.PDF - Radar Data (item 8, .PDF, 75 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40185255&FileExtension=.PDF&FileName=Radar%20Data-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 9, .PDF, 354 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442111&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 10, .PDF, 46 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442112&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF - Toxicological Report (item 11, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40442113&FileExtension=.PDF&FileName=Toxicological%20Report-Redacted.PDF - Photo 1. Approximate location of accident site looking south along flight path on the east side of the Mount Diablo ridgeline. Digital Image (item 12, .PDF, 253 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40187285&FileExtension=.PDF&FileName=Photo%201.%20%20Approximate%20location%20of%20accident%20site%20looking%20south%20along%20flight%20path%20on%20the%20east%20side%20of%20the%20Mount%20Diablo%20ridgeline.%20%20Digital%20Image-Master.PDF - Photo 2. West side of Mount Diablo ridgeline looking toward southeast. Digital Image (item 13, .PDF, 183 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40187295&FileExtension=.PDF&FileName=Photo%202.%20%20West%20side%20of%20Mount%20Diablo%20ridgeline%20looking%20toward%20southeast.%20%20Digital%20Image-Master.PDF - Photo 3. Looking east down 60-degree slope toward accident site on west side of the ridgeline. Digital Image (item 14, .PDF, 284 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40187297&FileExtension=.PDF&FileName=Photo%203.%20%20Looking%20east%20down%2060-degree%20slope%20toward%20accident%20site%20on%20west%20side%20of%20the%20ridgeline.%20%20Digital%20Image-Master.PDF - Photo 4. Looking to the north through hole in tree canopy made by aircraft. Digital Image (item 15, .PDF, 298 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40187298&FileExtension=.PDF&FileName=Photo%204.%20%20Looking%20to%20the%20north%20through%20hole%20in%20tree%20canopy%20made%20by%20aircraft.%20%20Digital%20Image-Master.PDF - Photo 5. Inboard section of left wing at the 20-foot level in tree. Digital Image (item 16, .PDF, 300 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40187300&FileExtension=.PDF&FileName=Photo%205.%20%20Inboard%20section%20of%20left%20wing%20at%20the%2020-foot%20level%20in%20tree.%20%20Digital%20Image-Master.PDF - Photo 6. Outboard section (approximately 2/3) of the left wing and aileron. Digital Image (item 17, .PDF, 176 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40187301&FileExtension=.PDF&FileName=Photo%206.%20%20Outboard%20section%20(approximately%202%2F3)%20of%20the%20left%20wing%20and%20aileron.%20%20Digital%20Image-Master.PDF - Photo 7. Pieces of the right wing. Digital Image (item 18, .PDF, 175 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40187303&FileExtension=.PDF&FileName=Photo%207.%20%20Pieces%20of%20the%20right%20wing.%20%20Digital%20Image-Master.PDF - Photo 8. Tail section of the airplane in an inverted position. Digital Image (item 19, .PDF, 245 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40187305&FileExtension=.PDF&FileName=Photo%208.%20%20Tail%20section%20of%20the%20airplane%20in%20an%20inverted%20position.%20%20Digital%20Image-Master.PDF - Photo 9. Main wreckage area. Digital Image (item 20, .PDF, 261 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40187306&FileExtension=.PDF&FileName=Photo%209.%20%20Main%20wreckage%20area.%20%20Digital%20Image-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.