# NTSB LAX00LA281: Cessna 180, N3386D, North Las Vegas, NV, July 28, 2000 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 28, 2000, 09:10 local (16:10 UTC) - Place: North Las Vegas, NV - Coordinates: 36.139572, -115.180824 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.1396&lon=-115.1808&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report November 1, 2001 - Report: Approved by Office Director - NTSB case key (mKey): 49847 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX00LA281 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/49847/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=49847 - Page: https://openairdocs.org/ntsb/LAX00LA281 ## Probable cause The pilot's improper recovery from a bounced landing and subsequent failure to maintain directional control of the aircraft. Wind shear on landing approach was a factor in the accident. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight encounter with weather, approach - vfr pattern - final approach - weather condition - windshear (contributing factor) - Hard landing, landing - flare/touchdown - Loss of control - on ground/water, landing - roll - recovery from bounced landing - improper, pilot in command (cause) - directional control - not maintained, pilot in command (cause) - On ground/water encounter with terrain/water, landing - roll ## Analysis The pilot reported that he encountered wind shear and developed a high sink rate during an otherwise normal landing approach. A bounced landing resulted and, during the attempt to recover from the bounce, the aircraft bounced again and veered off the runway. The right-hand main landing gear separated and the aircraft came to rest off the runway. Tire marks on the runway indicated that the aircraft first landed about 1,600 feet from the approach end of the runway and then veered off the runway about 200 feet further down the runway. Marks in the dirt indicated that the airplane then paralleled the runway for about 500 feet before becoming airborne again and travelling another 250 feet before coming to rest. ## Factual narrative On July 28, 2000, at 0910 hours Pacific daylight time, a Cessna 180, N3386D, was substantially damaged during a hard landing at North Las Vegas, Nevada. The commercial pilot and one passenger were not injured. The personal flight departed from the French Valley airport at Murrieta/Temecula, California at 0715. The flight was operated by the owner under 14 CFR Part 91, and no flight plan was filed. Visual meteorological conditions prevailed, and included light and variable winds and a 5,000-foot density altitude. The pilot reported that he encountered wind shear and developed a high sink rate during an otherwise normal landing approach to runway 7. A bounced landing resulted and, during the attempt to recover from the bounce, the aircraft bounced again and veered to the right off the runway. The right-hand main landing gear separated and the aircraft came to rest off the runway. An inspector from the Federal Aviation Administration Las Vegas Flight Standards District Office reported that tire marks on the runway indicated that the aircraft first landed about 1,600 feet from the approach end of runway 7, and then veered off the runway to the southeast about 200 feet further down the runway. Marks in the dirt indicated that the airplane then paralleled the runway for about 500 feet before becoming airborne again. The airplane finally came to rest about 250 feet further east on a southerly heading. ## Aircraft - Registration: N3386D (not matched to a registry record) - Reported make and model: Cessna 180 - Category: Airplane - Serial number: 32184 - Airframe hours: 2500 - Engines: Continental O-470K 230 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Ross J. Capawana - Airworthiness certificate: Standard, Normal - Last inspection: Annual, June 1, 2000, 15 hours before - Departed: F70, TEMECULA, CA - Destination: VGT - Airport: VGT, North Las Vegas, runway 7, 5,005 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 61; commercial; airplane ratings: multi-engine sea, single-engine land, multi-engine land, single-engine sea; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: left; flight hours: 5,200 total, 250 in this make and model, 4,800 as pilot in command, 30 in the last 90 days, 10 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 4 knots - Visibility: 15 statute miles - Lowest ceiling: none - Temperature: 201 °F, dew point 81 °F - Altimeter: 29.00 inHg - Observed at: VGT ## 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 20000728007639A](https://openairdocs.org/incident/20000728007639A), Jul 28, 2000: Cessna 180, Las Vegas, NV, No damage. (-23) At approximately 715 am on July 28, 2000, Cessna N3386D departed french valley airport (F70) for its home base, north Las Vegas (vgt). The aircraft… ## Docket (2 files) The files NTSB released with the investigation on October 10, 2001, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=49847. 459 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 344 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40423630&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Reports from Federal Agencies, FAA Las Vegas FSDO (item 2, .PDF, 115 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40148232&FileExtension=.PDF&FileName=Reports%20from%20Federal%20Agencies,%20FAA%20Las%20Vegas%20FSDO-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.