Piper PA-28R-200 and Piper PA-46-350P accident near North Las Vegas, Nevada, September 23, 2003
On September 23, 2003 at about 7:55 pm local time, 2 aircraft, Piper PA-28R-200 (N8604N) and Piper PA-46-350P (N146PM), were involved in the same accident near North Las Vegas, Nevada (North Las Vegas airport). 2 people were seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
the failure of the Federal Aviation Administration Air Traffic Control Tower local controller and local assist controller to effectively monitor the runway operation and ensure proper separation was maintained between aircraft on intersecting runways.
the failure of the Federal Aviation Administration Air Traffic Control Tower local controller and local assist controller to effectively monitor the runway operation and ensure proper separation was maintained between aircraft on intersecting runways.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 23, 2003 · about 7:55 pm local time
- Place
- North Las Vegas, Nevada · North Las Vegas · map
- Type
- Accident · collision on the ground
- Injuries
- 2 people were seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Piper PA-28R-200 · all PA-28R-200s on the register
- Registration
- N8604N · no longer on the register · serial 28R-7135124
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
- Aircraft 2
- Piper PA-46-350P · all PA-46-350Ps on the register
- Registration
- N146PM · registry record · serial 4622160
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative for the Piper PA-28R-200 final · quoted from the NTSB record
The Piper Arrow (N8604N) was landing on runway 12R and the Piper Mirage (N146PM) had started the takeoff roll on runway 7 when they collided at the intersection of the two runways. The Piper Arrow was cleared to land on runway 12R, 54 seconds before the Piper Mirage was given a takeoff clearance on the intersecting runway. During this time frame, the local controller and local assist controller were both viewing the D-Brite radar and looking out the tower cab's rear windows for a helicopter that had entered the class D airspace without authorization. With both controllers attention diverted to the helicopter, they failed to effectively monitor the runway operation and did not ensure proper separation was maintained between the two airplanes operating on the intersecting runways. Radar data indicated when the pilot of the Piper Arrow contacted the LC-1 controller and reported inbound for landing, the airplane was approximately 6 miles north-northeast of the airport and tracking a course of about 200 degrees. The airplane remained on that course, and the pilot was cleared to land when the airplane was approximately 2 1/4 miles north-northwest of the airport. About 20 seconds later the airplane began a left turn towards the airport. The airplane’s radar track indicated the pilot of the Piper Arrow flew a standard base leg to final approach, in accordance with the issued clearance. When the LC-1 controller cleared the pilot of the Piper Mirage for takeoff, the Piper Arrow was about 1 1/2 miles northeast of the airport on final to runway 12R with the data tag on the D-Brite radar showing a ground speed of 110 knots. Assuming that Piper Arrow’s ground speed remained 110 knots or less during the remainder of the approach, the airplane was about 1 minute away from touchdown. This meant that the pilot of the Piper Mirage had less than 1 minute to power up his aircraft, taxi on to runway 7, begin a departure roll, and travel about 725 feet in order to pass through the intersection of runway 12R before the Piper Arrow crossed the landing threshold for runway 12R. While this is not impossible, the minimal time available for Piper Mirage to depart before the Piper Arrow arrived warranted close monitoring by the controllers to ensure that separation was maintained at the intersection.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The NTSB's narrative for the Piper PA-46-350P final · quoted from the NTSB record
The Piper Arrow (N8604N) was landing on runway 12R and the Piper Mirage (N146PM) had started the takeoff roll on runway 7 when they collided at the intersection of the two runways. The Piper Arrow was cleared to land on runway 12R, 54 seconds before the Piper Mirage was given a takeoff clearance on the intersecting runway. During this time frame, the local controller and local assist controller were both viewing the D-Brite radar and looking out the tower cab's rear windows for a helicopter that had entered the class D airspace without authorization. With both controllers attention diverted to the helicopter, they failed to effectively monitor the runway operation and did not ensure proper separation was maintained between the two airplanes operating on the intersecting runways. Radar data indicated when the pilot of the Piper Arrow contacted the LC-1 controller and reported inbound for landing, the airplane was approximately 6 miles north-northeast of the airport and tracking a course of about 200 degrees. The airplane remained on that course, and the pilot was cleared to land when the airplane was approximately 2 1/4 miles north-northwest of the airport. About 20 seconds later the airplane began a left turn towards the airport. The airplane's radar track indicated the pilot of the Piper Arrow flew a standard base leg to final approach, in accordance with the issued clearance. When the LC-1 controller cleared the pilot of the Piper Mirage for takeoff, the Piper Arrow was about 1 1/2 miles northeast of the airport on final to runway 12R with the data tag on the D-Brite radar showing a ground speed of 110 knots. Assuming that Piper Arrow's ground speed remained 110 knots or less during the remainder of the approach, the airplane was about 1 minute away from touchdown. This meant that the pilot of the Piper Mirage had less than 1 minute to power up his aircraft, taxi on to runway 7, begin a departure roll, and travel about 725 feet in order to pass through the intersection of runway 12R before the Piper Arrow crossed the landing threshold for runway 12R. While this is not impossible, the minimal time available for Piper Mirage to depart before the Piper Arrow arrived warranted close monitoring by the controllers to ensure that separation was maintained at the intersection.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record for the Piper PA-28R-200 from the NTSB's investigation tables, in plain English
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 412 hours in all; 26 in this make and model; 6 in the last 90 days; 3 in the last 30 days; 335 as pilot in command
- Last flight review: July 16, 2002
- Medical certificate: Class 3 (valid medical--no waivers/lim.)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 4,524 hours
- Last inspection: annual inspection, July 1, 2003; 35 hours since
- Maximum gross weight: 2,600 lb
- Seats: 4
- Landing gear: retractable
- Engine: Lycoming IO-360 (piston); 0 hours total
- Fire on the ground
- Operator: West Air Aviation
The flight
- Departed from: SGU St. George UT at 7:00 pm
- Destination: VGT N. Las Vegas NV
- Flight plan: none
- Runway 12R, 5,000 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 130° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 86°F (30°C), dew point 41°F (5°C)
- Observation at 7:53 pm from VGT
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
The factual record for the Piper PA-46-350P from the NTSB's investigation tables, in plain English
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 1,756 hours in all; 88 in this make and model; 13 in the last 90 days; 68 in the last 30 days; 1,580 as pilot in command
- Last flight review: February 14, 2003
- Medical certificate: Class 2 (valid medical--w/ waivers/lim.)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 965 hours
- Last inspection: annual inspection, February 12, 2003; 68 hours since
- Maximum gross weight: 6,000 lb
- Seats: 6
- Landing gear: retractable
- Engine: Pratt & Whitney PT6A-35 (turboprop); 0 hours total
- Fire on the ground
The flight
- Departed from: VGT N. Las Vegas NV at 7:55 pm
- Destination: SLC Salt Lake City UT
- Flight plan: none
- Runway 7, 5,005 ft by 75 ft
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.