# NTSB LAX98LA270: Silvaire Luscombe 8F, N1616Z, Tucson, AZ, August 19, 1998 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: August 18, 1998, 17:36 local (Aug 19, 1998, 00:36 UTC) - Place: Tucson, AZ - Coordinates: 32.199707, -110.950859 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.1997&lon=-110.9509&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: Serious injuries - Injuries: 1 serious, 1 minor; on the ground: 1 minor - Status: Completed, report April 20, 2000 - Report: Approved by Office Director - NTSB case key (mKey): 43689 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX98LA270 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/43689/pdf - Page: https://openairdocs.org/ntsb/LAX98LA270 ## Probable cause The pilot's selection of the wrong runway for the wind conditions, his inadequate compensation for the existing quartering tailwind condition, and, his failure to maintain directional control. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - roll - weather condition - crosswind - weather condition - tailwind - compensation for wind conditions - inadequate, pilot in command (cause) - directional control - not maintained, pilot in command (cause) - wrong runway - selected, pilot in command (cause) - ground loop/swerve - inadvertent - On ground/water collision with object, landing - roll - object - fence - object - building(nonresidential) - object - vehicle ## Analysis Witnesses reported that the aircraft landed fast on the main wheels, began veering left off the runway, became airborne, touched down in a dirt area, became airborne again, went through a chain link fence, and collided with an occupied security truck in the Arizona Air National Guard compound. The airport was using runway 11 for takeoffs and landings. During initial contact with the Tucson Air Traffic Control Tower, the pilot had requested runway 3 for landing, and, the tower issued the requested clearance, along with the wind direction and speed of 280 degrees at 7 knots. The airframe and engine were examined following recovery with no discrepancies noted. ## Factual narrative On August 18, 1998, at 1736 hours mountain standard time, a Silvaire Luscombe 8F, N1616Z, veered off runway 3 while landing at the Tucson, Arizona, International Airport. The aircraft, which was destroyed, damaged an Air National Guard (ANG) fence, and substantially damaged an ANG security truck. The commercial pilot sustained serious injuries and the driver of the truck incurred minor injuries. The aircraft was owned and operated by the pilot under the provisions of 14 CFR Part 91 of the Federal Aviation Regulations. Visual meteorological conditions prevailed and included winds from 280 degrees at 8 knots. The flight originated from Falcon Field, Mesa, Arizona at 1630. There was no flight plan filed for the personal flight. The pilot is a military aviator with the Arizona Air National Guard, stationed at the Tucson Airport, and flies the F-16. In his written report, the pilot stated that during contact with the Tucson Air Traffic Control Tower, he had requested runway 3 for landing. The tower issued the requested clearance along with the wind direction and speed, which was 280 degrees at 7 knots. He said that just before the tail wheel touched the ground, the plane veered left and he applied right rudder to no avail. He went on to state that he applied full power for a go-around, rotated the aircraft, but the engine did not respond and he was unable to make a successful climb. He clipped the fence and collided with the roof of a parked security truck behind the first row of F-16's. Witnesses reported that the aircraft landed fast on the main wheels, began veering left off the runway, became airborne, touched down in a dirt area, became airborne again, went through a chain link fence, and collided with an occupied security truck in the Arizona Air National Guard compound. Following recovery of the aircraft to a salvage facility in Phoenix, Arizona, the Safety Board examined the airframe and engine. No discrepancies were noted with the airframe. With a supply of fuel plumbed into the aircraft fuel lines at the wing root, the engine was started and found to respond to throttle inputs. ## Aircraft - Registration: N1616Z (not matched to a registry record) - Reported make and model: Silvaire LUSCOMBE 8F (LUSCOMBE 8) - Category: Airplane - Serial number: S-72 - Airframe hours: 1569 - Engines: Lycoming O-320-A2B 150 horsepower reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Registered owner: Samuel D. Lee - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 2, 1998, 126 hours before - Departed: FFZ, MESA, AZ - Destination: TUS - Airport: TUS, Tucson Int'L Airport, runway 3, 4,201 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 34; commercial, military; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, valid medical--no waivers/lim.; seat: left; flight hours: 2,187 total, 20 in this make and model, 1,614 as pilot in command, 72 in the last 90 days, 25 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 280° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 91 °F, dew point 55 °F - Altimeter: 29.00 inHg - Observed at: TUS ## 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 19980818021239A](https://openairdocs.org/incident/19980818021239A), Aug 18, 1998: Luscom 8F, Tucson, AZ, Destroyed. Acft lost control on landing and veered left, became airborne, veered right, struck an air national guard truck. Came to rest on parking ramp. (.4) witnesses… 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.