# Accident 20030923037052A: Piper PA46350P, Las Vegas, NV, September 23, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 23, 2003, 12:55 local time
- Place: Las Vegas, NV
- Airport: North Las Vegas Air Terminal
- Damage: Substantial damage
- Collision: Midair collision, second aircraft
- Phase of flight: Takeoff Ground Roll
- Operating rules: General operating rules (Part 91)
- Location: 36.2125° N, 115.1961° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.2125&lon=-115.1961&mi=10
- Aircraft: N146PM (not matched to a registry record)
- Reported make and model: PIPER PA46350P
- Fatal injuries: 0
- Pilot flight hours: 1,850 total
- NTSB investigation: [NTSB LAX03FA298](https://openairdocs.org/ntsb/LAX03FA298) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030923037052A

## Narrative

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

(-23) ATC HAD ISSUED THE PILOT OF N146PM A TAKE OFF CLEARANCE FOR RUNWAY 07 AND A LANDING CLEARANCE FOR RUNWAY 12R TO THE PILOT OF N8604N. THE AIRCRAFT COLLIDED AT THE INTERSECTION OF THE RUNWAYS. NEITHER PILOT OBSERVED THE OTHER PRIOR TO THE COLLISION.

## Other aircraft in the event

- N8604N, Piper PA28R200: [Accident 20030923037051A](https://openairdocs.org/incident/20030923037051A)

## 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 LAX03FA298](https://openairdocs.org/ntsb/LAX03FA298), Sep 23, 2003: Piper PA-46-350P (N146PM), North Las Vegas, NV, substantial damage. Probable cause: 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…

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.