- Date
- April 10, 1999, 09:30 local (16:30 UTC)
- Place
- North Las Vegas, NV
- Injuries
- 3 uninjured
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N3289LCessna 172H
- Weather
- Visual (VMC) · Day
- Status
- Completed · report January 18, 2001
- Report
- Approved by Office Director
- FAA report
- 19990410019409A
- Case key
- 46090
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
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.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
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 regain control of the aircraft and the nose wheel collided with a taxiway sign. He said he then was finally able to regain aircraft control and took the aircraft around the traffic pattern and landed on runway 7. As the nose wheel touched down, the nose strut collapsed. Subsequent examination of the aircraft revealed damage to the firewall and right horizontal stabilizer.
Factual narrative
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 aircraft 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 not 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 regain control of the aircraft and the nose wheel collided with a taxiway sign. He said he then was finally able to regain aircraft control and took the aircraft around the traffic pattern and landed on runway 7. As the nose wheel touched down, the nose strut collapsed. Subsequent examination of the aircraft revealed damage to the firewall and right horizontal stabilizer.
Aircraft
- Registration
- N3289L
- Reported as
- Cessna 172H
- Category
- Airplane
- Serial number
- 17256189
- Airframe hours
- 4,100
- Engine
- Continental O-300D, 145 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- North Las Vegas Flying Club
- Registered owner
- David R. Burns
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · March 9, 1999 · 38 hours before
- Departed
- VGT
- Destination
- GCN · Grand Canyon, AZ
- Airport
- VGT · North Las Vegas, runway 30, 5,000 × 75 ft, asphalt
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 29
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 2, Valid Medical--no waivers/lim.
- Seat
- Left
- Flight hours
- 52 total · 52 in this make and model · 25 as pilot in command · 6 in the last 90 days · 2 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 70° at 5 knots
- Visibility
- 25 statute miles
- Lowest ceiling
- None
- Temperature
- 64 °F
- Altimeter
- 30.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.