# Accident 19990410019409A: Cessna 172H, Las Vegas, NV, April 10, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 10, 1999, 09:30 local time
- Place: Las Vegas, NV
- Airport: North Las Vegas Air Terminal
- Damage: Substantial damage
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: General operating rules (Part 91)
- Location: 36.2105° N, 115.1191° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=36.2105&lon=-115.1191&mi=10
- Aircraft: N3289L, a cancelled registration (https://openairdocs.org/deregistered/N3289L-2024-02-09) (OpenAirDocs)
- Registry model: Cessna 172H (registry code 2072424, https://openairdocs.org/model/cessna-172h) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: CESSNA 172H
- Reported engine: CONT O300*
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 6 total, 50 in this make and model, 50 in the last 90 days
- NTSB investigation: [NTSB LAX99LA145](https://openairdocs.org/ntsb/LAX99LA145) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990410019409A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON APRIL 10, 1999, AT 0930 HOURS PACIFIC DAYLIGHT TIME, A CESSNA 172H, N3289L, VEERED RIGHT OFF RUNWAY 30 AND COLLIDED WITH A TAXIWAY SIGN DURING TAKEOFF FROM THE NORTH LAS VEGAS, NEVADA, AIRPORT. THE ACFT WAS OPERATED BY NORTH LAS VEGAS FLYING CLUB AND WAS RENTED BY THE PILOT FOR A PERSONAL CROSS-COUNTRY FLIGHT UNDER 14 CFR PART 91 OF THE FEDERAL AVIATION REGULATIONS.  VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME AND NO FLIGHT PLAN WAS FILED.  THE AIRCRAFT INCURRED SUBSTANTIAL DAMAGE.  THE PRIVATE PILOT AND HIS TWO PASSENGERS WERE NO INJURED.  THE FLIGHT WAS ORIGINATING AT THE TIME AS A CROSS-COUNTRY FLIGHT TO THE GRAND CANYON NATIONAL PARK AIRPORT.  IN A WRITTEN STATEMENT, THE PILOT REPORTED THAT HE WAS ATTEMPTING A FORMATION TAKEOFF WITH ANOTHER AIRCRAFT AND INITIATED HIS TAKEOFF ROLL WHEN THE FIRST AIRCRAFT BECAME AIRBORNE.  AT 65 MPH, THE PILOT ROTATED AND THE AIRCRAFT VEERED RIGHT JUST AS THE WHEELS LEFT THE GROUND.  THE PILOT STATED THAT HE WAS UNABLE TO RAIN CONTROL OF THE ACFT AND THE NOSE WHEEL COLLIDED WITH A TAXIWAY SIGN.  HE SAID HE THEN WAS FINALLY ABLE TO REGAIN ACFT CONTROL AND TOOK THE ACFT AROUND THE TRAFFIC PATTERN AND LANDED ON RUNWAY 7.  AS THE NOSE  WHEEL TOUCHED DOWN, THE NOSE STRUT COLLAPSED. SUBSEQUENT EXAMINATION OF THE ACFT REVEALED DAMAGE TO THE FIREWALL AND RIGHT HORTIZONTAL STABLIZER.    (-23)THE PILOT OF N3289L LOST CONTROL OF HIS AIRCRAFT FOR UNKNOWN REASONS SHORTLY AFTER ROTATION. THE AIRCRAFT VEERED TO THE RIGHT, STRIKING AND DESTROYING A LARGE TAXIWAY SIGN DISPLACED APPROXIMATELY 67 FEET FROM THE RUNWAY CENTERLINE.  THE PILOT REGAINED CONTROL OF THE AIRCRAFT AND LEFT THE AIRPORT TRAFFIC AREA LONG ENOUGH TO ALLOW ANOTHER PILOT TO APPROACH AND INSPECT HIS AIRCRAFT.  WHEN THE PILOT RETURNED TO THE AIRPORT TO LAND, HE LANDED FLAT AND HARD, BOUNCING AT LEAST ONCE.  ABOUT 600' FROM INITIAL TOUCHDOWN.  THE NOSEGEAR DEPARTED THE AIRCRAFT.  THE AIRCRAFT THEN SKIDDED ON ITS NOSE APPROXIMATELY 100' BEFORE COMING TO REST.  THE RESULTING SUBSTANTIAL DAMAGE INCLUDING THE FIREWALL, ENGINE, PROPELLER AND RIGHT HORIZONTAL STABILIZER.

## The NTSB's investigation of this event (1)

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.

- [NTSB LAX99LA145](https://openairdocs.org/ntsb/LAX99LA145), Apr 10, 1999: Cessna 172H (N3289L), North Las Vegas, NV, substantial damage. Probable cause: The pilot's failure to maintain directional control during takeoff roll resulting in a collision with taxiway sign. A factor was the sign.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.