The U.S. aircraft register, updated daily
Accidents · NTSB WPR18LA003 · Final report

Amateur-built LONG EZ and Piper PA 28-180 mid-air collision near Tucson, Arizona, October 7, 2017

On October 7, 2017 at about 5:30 pm local time, 2 aircraft, amateur-built LONG EZ (N966EZ) and Piper PA 28-180 (N15664), were involved in a mid-air collision near Tucson, Arizona (Ryan Field). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The failure of both pilots to see and avoid the other airplane while maneuvering in the traffic pattern, which resulted in a midair collision. Contributing to the accident was the controller's failure to provide adequate traffic information, issue necessary traffic advisories, and establish a safe traffic sequence for airplanes under his control in the Class D airspace.
The failure of both pilots to see and avoid the other airplane while maneuvering in the traffic pattern, which resulted in a midair collision. Contributing to the accident was the controller's failure to provide adequate traffic information, issue necessary traffic advisories, and establish a safe traffic sequence for airplanes under his control in the Class D airspace.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 7, 2017 · about 5:30 pm local time · cases in 2017
Place
Tucson, Arizona · Ryan Field · cases near this airport · map
Type
Accident · mid-air collision
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft 1
Amateur-built LONG EZ NO SERIES, built 1986
Registration
N966EZ · no longer on the register · serial 966
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)
Aircraft 2
Piper PA 28-180 180, built 1972 · all PA 28-180s on the register
Registration
N15664 · registry record · serial 28-7305113
Damage
Minor damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative for the amateur-built LONG EZ final · quoted from the NTSB record

Two airplanes, a Long EZ and a Piper PA-28, collided in midair while in the traffic pattern about 1 mile northwest of the airport. The Long EZ pilot reported to the air traffic control (ATC) tower about 9 miles north of the airport that he was inbound for a full-stop landing. The controller instructed the Long EZ pilot to make left traffic to runway 6L and to report 2 miles on the 45° to runway 6L, which the pilot acknowledged. About 1 minute later, the Piper pilot reported about 8.5 miles northwest of the airport that he was inbound for a full-stop landing. He was instructed to enter a left base for runway 6L, which he acknowledged. The controller then instructed the Long EZ pilot to make a left 360° turn for traffic, which the pilot acknowledged. He then cleared the Long EZ to be “number two” to land on runway 6L, following a Cessna on a left base. The Long EZ pilot acknowledged his clearance. Shortly thereafter, two garbled transmissions were made. The controller then asked who was requesting runway 6R; the Long EZ pilot responded that he was not requesting runway 6R but wanted to confirm that traffic was landing on runway 6R. The controller stated that he had a Cessna on short final for runway 6L and a Piper Cherokee on about a 1-mile final for runway 6R. The Long EZ pilot transmitted that he had the wrong traffic in sight and that he now had the other landing traffic in sight on final. The controller told the Long EZ pilot to follow the traffic just over the numbers on runway 6L. The Long EZ pilot stated that while he was on downwind, he saw a Piper “passing rapidly directly above” him from the right. According to the Piper pilot, he began his turn for a left base to the runway when he noticed an airplane coming toward him from downwind. He further stated that he attempted to avoid the other airplane but that his airplane's landing gear struck the Long EZ. Both airplanes declared an emergency and landed uneventfully. The Long EZ sustained substantial damage to the left rudder, and the Piper sustained minor damage to the landing gear assembly. The pilots of both airplanes had the final authority for the operation of their airplanes and were required to see and avoid other airplanes. Further, although no specific ATC separations were applicable during the visual flight rules pattern operation, the controller was still required to be vigilant for traffic conflicts, provide traffic information and issue traffic advisories when necessary, and establish a safe traffic sequence to the runway.

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 28-180 final · quoted from the NTSB record

Two airplanes, a Long EZ and a Piper PA-28, collided in midair while in the traffic pattern about 1 mile northwest of the airport. The Long EZ pilot reported to the air traffic control (ATC) tower about 9 miles north of the airport that he was inbound for a full-stop landing. The controller instructed the Long EZ pilot to make left traffic to runway 6L and to report 2 miles on the 45° to runway 6L, which the pilot acknowledged. About 1 minute later, the Piper pilot reported about 8.5 miles northwest of the airport that he was inbound for a full-stop landing. He was instructed to enter a left base for runway 6L, which he acknowledged. The controller then instructed the Long EZ pilot to make a left 360° turn for traffic, which the pilot acknowledged. He then cleared the Long EZ to be “number two” to land on runway 6L, following a Cessna on a left base. The Long EZ pilot acknowledged his clearance. Shortly thereafter, two garbled transmissions were made. The controller then asked who was requesting runway 6R; the Long EZ pilot responded that he was not requesting runway 6R but wanted to confirm that traffic was landing on runway 6R. The controller stated that he had a Cessna on short final for runway 6L and a Piper Cherokee on about a 1-mile final for runway 6R. The Long EZ pilot transmitted that he had the wrong traffic in sight and that he now had the other landing traffic in sight on final. The controller told the Long EZ pilot to follow the traffic just over the numbers on runway 6L. The Long EZ pilot stated that while he was on downwind, he saw a Piper “passing rapidly directly above” him from the right. According to the Piper pilot, he began his turn for a left base to the runway when he noticed an airplane coming toward him from downwind. He further stated that he attempted to avoid the other airplane but that his airplane's landing gear struck the Long EZ. Both airplanes declared an emergency and landed uneventfully. The Long EZ sustained substantial damage to the left rudder, and the Piper sustained minor damage to the landing gear assembly. The pilots of both airplanes had the final authority for the operation of their airplanes and were required to see and avoid other airplanes. Further, although no specific ATC separations were applicable during the visual flight rules pattern operation, the controller was still required to be vigilant for traffic conflicts, provide traffic information and issue traffic advisories when necessary, and establish a safe traffic sequence to the runway.

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 amateur-built LONG EZ from the NTSB's investigation tables, in plain English

What happened, in order

  1. Midair collision during approach (VFR pattern downwind) defining event

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
  • cause Personnel issues › Task performance › Communication (personnel) › Issuing instructions › ATC personnel

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,247 hours in all; 1,093 in this make and model; 17 in the last 90 days; 6 in the last 30 days; 1,219 as pilot in command
  • Last flight review: May 24, 2017
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: frt
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,093 hours
  • Last inspection: condition inspection, June 15, 2017
  • Seats: 2
  • Landing gear: retractable
  • Engine: Lycoming O-320 E2G (piston); 3,026 hours total

The flight

  • Departed from: P13 Globe AZ at 5:00 pm
  • Destination: RYN Tucson AZ
  • Flight plan: none
  • Runway 06L, 4,900 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 090° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 81°F (27°C), dew point 14°F (-10°C)
  • Altimeter: 29.92 inHg
  • Observation at 4:58 pm from DMA, 149 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

The factual record for the Piper PA 28-180 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Midair collision during approach (VFR pattern base) defining event

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
  • cause Personnel issues › Task performance › Communication (personnel) › Issuing instructions › ATC personnel

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Medical certificate: Unknown
  • Seat: left
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Last inspection: inspection type not recorded
  • Landing gear: fixed
  • Engine: Lycoming O&VO-360 SER (piston); 0 hours total

The flight

  • Departed from: CHD Chandler AZ at 4:35 pm
  • Destination: RYN Tucson AZ
  • Flight plan: none
  • Runway 06L, 4,900 ft by 75 ft

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Other NTSB records under N966EZ the same tail number, which may have belonged to a different aircraft at the time

2021-07-27WPR21FA288 · accident near Tucson, AZ · substantial damage · fatal

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/WPR18LA003.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.