NYC03FA021 · Mooney M10
Mooney M10 and Piper PA-32R-300 · Accident: midair collision on approach
Event
- NTSB case
- NYC03FA021
- 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
Aircraft 1 · Mooney M10
- Aircraft type
- Mooney M10
- 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
- N9502V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Essex County Airport (CDW), Caldwell, NJTo Essex County Airport (CDW)
- 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
- 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
- Midair collision
- 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 · Piper PA-32R-300
- Aircraft type
- Piper PA-32
- 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
- N216CL
- Operator
- Paul J. DiSarro · private individual
- Onboard fatalities
- Unknown
- Route
- From Alexandria Field Airport (N85), Pittstown, NJTo Essex County Airport (CDW), Caldwell, NJ
- 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
- 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
- Midair collision
- 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 › Visual lookout, inadequate
- Pilot of other aircraft › Visual lookout, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A Mooney had completed a go-around, and was flying a right traffic pattern for runway 22. A Piper was entering the traffic pattern from the west, consistent with a 45-degree entry to a right downwind for runway 22. According to radar data, the Mooney was making a right turn toward a northeasterly direction, consistent with a crosswind to downwind leg for runway 22. The Piper was west of the Mooney target, and appeared to converge in an easterly direction. Three air traffic controllers were on duty at the time of the accident. Prior to the collision, two controllers were in the cab, and one controller was in the break room. The accident controller combined positions to let the second controller in the cab go out of the tower for a meal break. The third controller had been out of the cab for approximately 3 hours, but remained in the break room, which left only one controller in the cab. At that time, there were four aircraft in the traffic pattern, and the pilot of a fifth aircraft was requesting entry into the pattern. About 10 minutes later, with six airplanes in the traffic pattern, two pilots were cut-off and two pilots performed a go-around. One of the pilots subsequently stated that the controller was having difficulty correctly identifying the airplanes in the pattern. The pilot of the Piper had contacted the tower, and reported that he was 7.5 miles west of the airport at 2,500 feet. The controller instructed the pilot to report a right downwind leg for runway 22, but did not provide a sequence or traffic advisory. Additionally, the controller spent approximately 1 minute conversing with the pilot of a helicopter. When the collision occurred, the controller did not see it, nor did he provide traffic advisories to either pilot. The controller thought the Mooney would be ahead of the Piper in the traffic pattern. The weather was clear, and witnesses reported that both accident airplanes had lights illuminated. One witness stated that the Mooney converged into the Piper from the right, at an approximate 45-degree angle. A second witness stated that the Piper was in the traffic pattern, straight and level, when the Mooney appeared in a climbing right turn, converging on an approximate 45-degree angle. A third witness, who was a flight instructor, saw one airplane on a downwind leg that was struck by the other aircraft turning crosswind to downwind. The third witness added that it was possible the airplane on the downwind leg had entered the traffic pattern incorrectly. He further stated that both airplanes were well lit, and both accident pilots should have been able to see each other. The left wing of the Mooney exhibited several propeller strikes, cut at an approximate 45-degree angle to the wing chordline, and progressing toward the cockpit. Toxicological testing for the pilot of the Piper revealed Butalbital in the blood and urine. However, the level of Butalbital found in the blood suggested that the pilot had not taken the drug in well over 24 hours prior to the accident.
Probable cause
The inadequate visual lookout of both pilots. Factors in the accident were the FAA controller's failure to provide a traffic advisory, the improper decision among the three controllers to leave only one controller in the cab, and night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC03FA021
- Event ID
- 20021120X05496
- Case number
- NYC03FA021
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-11-16.
- API snapshot SHA-256: c07fb024cc771fdd14fc6ee61e151b895b440d5ba34c5b18deaca59394c971a0; retrieved 2026-09-20T19:39:52.162Z.