# NTSB LAX03LA006: Cessna 310L, N2209F, North Las Vegas, NV, October 13, 2002

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: October 12, 2002, 23:20 local (Oct 13, 2002, 06:20 UTC)
- Place: North Las Vegas, NV
- Coordinates: 36.211666, -115.195831
- Nearby events: https://openairdocs.org/map.md?lat=36.2117&lon=-115.1958&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 5 uninjured
- Status: Completed, report October 28, 2004
- Report: Approved by Office Director
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 55864
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX03LA006
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/55864/pdf
- Page: https://openairdocs.org/ntsb/LAX03LA006

## Probable cause

The pilot's failure to use the landing checklist due to his diverted attention, which resulted in a wheels-up landing.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Wheels up landing, landing - flare/touchdown
  - diverted attention, pilot in command (contributing factor)
  - checklist - not used, pilot in command (cause)

## Analysis

During the pilot's approach for landing he became distracted looking for traffic, failed to complete the airplane's landing checklist, and slid to a stop on the runway with retracted landing gear.  The pilot indicated that because he had been slightly low on the final approach course, he had maintained engine power.  The pilot did not notice that the airplane's green landing gear down lights were not illuminated.  No mechanical malfunctions were experienced.

## Factual narrative

On October 12, 2002, about 2320 Pacific daylight time, a Cessna 310L, N2209F, was substantially damaged during landing at the North Las Vegas Airport, North Las Vegas, Nevada.  The airplane slid to a stop on runway 30L with its landing gear fully retracted.  Neither the commercial pilot nor the four passengers were injured.  No flight plan had been filed for the local area personal flight, and visual meteorological conditions prevailed at the time of the accident.  The flight was performed under the provisions of 14 CFR Part 91, and it originated from the airport about 2245.

The pilot reported to the National Transportation Safety Board investigator that while performing his prelanding checklist he became distracted looking for traffic, and he forgot to extend the landing gear.  The pilot stated that he was slightly low on the final approach course, so he maintained engine power.  He did not notice that the airplane's green landing gear down lights were not illuminated.

The pilot additionally stated that as he retarded the engines' throttles for landing, he heard the landing gear warning horn activate.  Nearly 1 second later, the airplane's propellers contacted the runway's surface.  The airplane slid to a stop, veered off the runway, and entered the gravel-surfaced median that, according to the pilot, caused it to yaw about 180 degrees.  The airplane came to rest with about a 2-foot-long span of the right wing extended over the runway.

The pilot also reported that he owned and operated the airplane.  No mechanical malfunctions were experienced with the airplane during the flight.

At the time of the accident, the airport's air traffic control tower had closed for the evening.  Following the accident, the local airport security officer and Federal Aviation Administration (FAA) air traffic control personnel (at another airport) were notified that the airplane had come to rest on the runway and was disabled.  The airplane remained on the runway overnight.  The FAA's flight service station was not notified of the mishap, and no notice to airman (NOTAM) was issued.  About 0545 the following morning (prior to dawn), a departing airplane using runway 30L reported experiencing a near miss with the disabled airplane.

## Aircraft

- Registration: [N2209F](https://openairdocs.org/deregistered/N2209F-2007-05-17), registration cancelled 2007-05-17, S/N 310L-0009, built 1966 (OpenAirDocs)
- Reported make and model: Cessna 310L
- Registry model: [Cessna 310L](https://openairdocs.org/model/cessna-310l) (registry code 2074230) (OpenAirDocs)
- Registry engine: [Continental I0-470 series](https://openairdocs.org/engine/continental-i0-470-series) (registry code 17027, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 310L-0009
- Engines: Continental IO-470V 260 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Lyle Scott Brooksby
- Registered owner: Aircraft Instruction and Rental, Inc.
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, October 10, 2001
- Departed: VGT, North Las Vegas, NV
- Destination: VGT, North Las Vegas, NV
- Airport: VGT, North Las Vegas, runway 30L, 5,000 × 75 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 46; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; last flight review October 27, 2001; seat: left; flight hours: 1,081 total, 422 in this make and model, 1,081 as pilot in command, 47 in the last 90 days, 9 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Night/dark
- Wind: 300° at 3 knots
- Visibility: 10 statute miles
- Lowest ceiling: none

## 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 20021012026749A](https://openairdocs.org/incident/20021012026749A), Oct 12, 2002: Cessna 310L, Las Vegas, NV, Substantial damage. (-23) On October 12, 2002, at 12:45 pilot stated he departed north Las Vegas airport (vgt) on runway 30L. Shortly after takeoff pilot contacted Las Vegas…

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.
