FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX01FA274 · Piper PA-28-180

12 Aug 2001 · Boulder City, NV, United States

Piper PA-28-180 · Accident: in flight collision with object on approach

From 61B · Boulder City, NV to 61B · Boulder City, NV

Report a problem

Event

NTSB case
LAX01FA274
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-28-180

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N8098W
Operator
Unknown
Onboard fatalities
Unknown
Route
From 61B · Boulder City, NVTo 61B · Boulder City, NV
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Utility pole
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › Impairment(alcohol)

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane collided with power lines and poles 1.1 miles east of the airport's runway 27 approach end while on a night visual landing approach. The accident site is in level desert terrain approximately the same elevation as the airport. Impact marks and transfers disclosed that the aircraft contacted a steel and concrete power pole and associated static and transmission lines with the left wing, center windshield post, and vertical stabilizer. Investigation revealed that the pilot and passenger had consumed alcoholic beverages during dinner together at a local restaurant the night of the accident. Following dinner, the pair were observed to consume other alcoholic beverages at a party. The airplane then departed from the airport, where the airplane is based, at an unknown time for a presumed local flight. An airborne witness was piloting an emergency medical services helicopter (based at the airport), which was returning from a mission and inbound to the airport from the south. He observed the position lights of the accident airplane approach the airport from the west through a pass, which crosses the mountains between the valley where the airport is located and the greater Las Vegas metropolitan area. The position lights were roughly at the same elevation as his helicopter, 4,000 feet msl. He attempted to contact the airplane on the Common Traffic Advisory Frequency, but got no response. As he continued inbound to the airport, he monitored the position of the airplane and saw it on a wide arcing flight path to the south of the airport. As he was beginning a final descent to land at their parking spot, the airplane's pilot came on the CTAF and announced that he was going to make a "teardrop approach" to runway 27 left. The witness said the pilot's voice had an unusual and strange quality and that the comment about a teardrop approach confused him momentarily because he knew that there was no such instrument approach to the airport. He then observed the airplane continue the wide arcing and descending left-hand flight path to runway 27. The witness had landed and was shutting the helicopter down when he looked up and observed the navigation lights of the airplane on final approach. He thought to himself that the airplane was very low, then he saw the bright flash of arcing electricity as the airplane contacted the power lines. The power lines contacted by the airplane are the most eastern of four sets of high tension power lines running perpendicular to the approach end of the runway. The pole and lines contacted by the airplane were 66 feet above ground level and on the extended runway centerline. The most western set of the three power line sets were marked by red obstruction lights. The sky was clear and the winds calm, with no moon visible. The airport's runway and approach lights were functioning. The airport is located on the south side of the city and, for an airplane on final approach, the airport lights would be the only ground reference lights visible. No pre-impact mechanical malfunctions or failures were identified with the airplane or engine. Ethanol was found in the following levels in specimens from the pilot: 124 mg/dl in blood, 74 mg/dl in brain, and 214 mg/dl in urine.

Probable cause

the pilot's failure to maintain an adequate terrain and obstruction clearance altitude while maneuvering in a non-standard visual approach to land. The pilot's misjudgment of his altitude and distance from the airport was due to impairment by alcohol. Factors in the accident were the dark nighttime lighting conditions and the visual perception difficulty created by a lack of ground reference lights.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX01FA274
Event ID
20010821X01746
Case number
LAX01FA274
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 2bb7f4f5d072be9dae1d220e657ba7653a432a8f811c0fac63034d3f352fbbf6; retrieved 2026-09-20T20:24:48.207Z.