NYC06LA042 · Piper PA-46-310P
Piper PA-46-310P and Smith, Ted Aerostar 601P · Accident: on ground/water collision with object during landing
Event
- NTSB case
- NYC06LA042
- 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
- 0 · 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
Aircraft 1 · Piper PA-46-310P
- Aircraft type
- Piper PA-46
- 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
- N302H
- Operator
- Richard Schneider
- Onboard fatalities
- Unknown
- Route
- From N99 · West Chester, PATo Chautauqua County-Dunkirk Airport (DKK), Dunkirk, NY
- 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
- Landing · landing roll
- 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
- On ground/water collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Smith, Ted Aerostar 601P
- Aircraft type
- Smith Ted Aerostar 601
- 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
- N1WZ
- Operator
- Antoine Attea
- Onboard fatalities
- Unknown
- Route
- From Chautauqua County-Jamestown Airport (JHW), Jamestown, NYTo Chautauqua County-Dunkirk Airport (DKK), Dunkirk, NY
- 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
- Landing · landing roll
- 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
- On ground/water collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Traffic advisory, incorrect
- Pilot in command › Wrong runway, selected
- Pilot of other aircraft › Traffic advisory, incorrect
- Pilot of other aircraft › Wrong runway, selected
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
An Aerostar landed on runway 15, a Piper Malibu landed on runway 6, and their right wings contacted at the runway intersection. The pilot of the Aerostar utilized the current Unicom frequency, and was told the winds were favoring runway 15, which was the active runway. The pilot of the Aerostar flew a left traffic pattern for runway 15, radioed position reports, and monitored a Cessna that was also in the traffic pattern for runway 15. The pilot of the Aerostar did not observe any other traffic as he landed on runway 15. The pilot of the Piper Malibu reported a 9-mile final for runway 6, on a radio frequency that had been out-of-date for longer than one year. The pilot of the Piper Malibu did not observe any traffic, and proceeded to land on runway 6. The pilot of the Piper Malibu was using a global positioning system, and did not refer to his onboard approach charts, which listed the correct frequency. The reported wind about the time of the accident was from 130 degrees at 11 knots.
Probable cause
The Piper Malibu pilot's failure to use the correct radio frequency for traffic advisories, and his selection of the wrong, inactive runway, which resulted in an on-ground collision with another airplane while landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06LA042
- Event ID
- 20051220X01994
- Case number
- NYC06LA042
- 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: 1e588ce842a719fac4e9f4eebd9bf373aadd0badec8426474265cb31cacbb3ab; retrieved 2026-09-22T05:12:04.282Z.