Piper J3C and Piper J3C mid-air collision near Weslaco, Texas, November 3, 2020
On November 3, 2020 at about 11:53 pm local time, 2 aircraft, Piper J3C (N87715) and Piper J3C (N6463H), were involved in a mid-air collision near Weslaco, Texas (Mid Valley Airport). 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
The pilot of N87715 inadvertently allowed his airplane to drift right of the runway during the climb after a touch-and-go landing, and the pilot of N6463H did not maintain adequate separation from the other airplane during his go-around. Contributing to the accident was the lack of two-way radio communication equipment in both airplanes.
The pilot of N87715 inadvertently allowed his airplane to drift right of the runway during the climb after a touch-and-go landing, and the pilot of N6463H did not maintain adequate separation from the other airplane during his go-around. Contributing to the accident was the lack of two-way radio communication equipment in both airplanes.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 3, 2020 · about 11:53 pm local time
- Place
- Weslaco, Texas · Mid Valley Airport · map
- Type
- Accident · mid-air collision
- Injuries
- 1 person was seriously injured and 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Piper J3C 65, built 1958 · all J3Cs on the register
- Registration
- N87715 · no longer on the register · serial 15373
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
- Aircraft 2
- Piper J3C 65, built 1946 · all J3Cs on the register
- Registration
- N6463H · registry record · serial 19641
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative for the Piper J3C final · quoted from the NTSB record
The pilots of two Piper J3C-65 airplanes, N87715 and N6463H, were conducting personal flights in the airport traffic pattern when they collided inflight. The pilot of N87715 reported that during the climb following a touch-and-go landing, he inadvertently allowed the airplane’s ground track to drift right of the runway while his attention was diverted to the cockpit instruments, and his airplane collided with another airplane about 80 ft above the ground. The crash site was in a grass area located about 110 ft off the right side of runway. The pilot of N6463H reported that after turning from base leg to final approach, he realized that his airplane was too close to the airplane ahead of him (N87715) in the traffic pattern. He decided to go around and sidestepped to the right of the runway to provide separation from the other airplane. He maintained visual contact with the other airplane, keeping it at his 9-to-10 o’clock position and slightly below his position, as he continued his go-around. The pilot stated that shortly after he shifted his gaze to the right side of his airplane to assess if there were any additional impediments to his flight path, the other airplane “made an apparent right turn” and collided with his airplane. The pilot was unable to maintain control of his airplane after the collision and it descended to the ground intermingled with the other airplane. Neither airplane was equipped with an electrical system or handheld radio. The lack of two-way communication equipment limited the pilots’ ability to communicate their positions and intentions while operating in the airport traffic pattern.
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 J3C final · quoted from the NTSB record
The pilots of two Piper J3C-65 airplanes, N87715 and N6463H, were conducting personal flights in the airport traffic pattern when they collided inflight. The pilot of N87715 reported that during the climb following a touch-and-go landing, he inadvertently allowed the airplane’s ground track to drift right of the runway while his attention was diverted to the cockpit instruments, and his airplane collided with another airplane about 80 ft above the ground. The crash site was in a grass area located about 110 ft off the right side of runway. The pilot of N6463H reported that after turning from base leg to final approach, he realized that his airplane was too close to the airplane ahead of him (N87715) in the traffic pattern. He decided to go around and sidestepped to the right of the runway to provide separation from the other airplane. He maintained visual contact with the other airplane, keeping it at his 9-to-10 o’clock position and slightly below his position, as he continued his go-around. The pilot stated that shortly after he shifted his gaze to the right side of his airplane to assess if there were any additional impediments to his flight path, the other airplane “made an apparent right turn” and collided with his airplane. The pilot was unable to maintain control of his airplane after the collision and it descended to the ground intermingled with the other airplane. Neither airplane was equipped with an electrical system or handheld radio. The lack of two-way communication equipment limited the pilots’ ability to communicate their positions and intentions while operating in the airport traffic pattern.
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 J3C from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during initial climb defining event
The NTSB's findings
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Heading/course › Not attained/maintained
- Aircraft › Aircraft systems › Communications system › (general) › Not installed/available
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: student
- Flight time: 95 hours in all; 35 in the last 90 days; 15 in the last 30 days; 40 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: rear
- Injury: minor injuries
The aircraft
- Airframe total time: 4,393 hours
- Last inspection: annual inspection, October 25, 2020; 2 hours since
- Maximum gross weight: 1,220 lb
- Seats: 2
- Landing gear: fixed
- Engine: Continental A-65-8 (piston); 892 hours total
The flight
- Flight plan: none
- Runway 14, 6,002 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 100° at 8 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 11,000 ft
- Temperature: 73°F (23°C), dew point 54°F (12°C)
- Altimeter: 30.21 inHg
- Observation at 5:55 pm from TXW
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 |
The factual record for the Piper J3C from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during approach (VFR go-around) defining event
The NTSB's findings
- Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
- Aircraft › Aircraft systems › Communications system › (general) › Not installed/available
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 8,500 hours in all; 50 in this make and model; 120 in the last 90 days; 35 in the last 30 days; 3,100 as pilot in command; 0 on instruments
- Last flight review: January 25, 2020
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: rear
- Injury: serious injuries
The aircraft
- Airframe total time: 3,816 hours
- Last inspection: annual inspection, October 25, 2020
- Maximum gross weight: 1,200 lb
- Seats: 2
- Landing gear: fixed
- Engine: Continental C-85 (piston); 0 hours total
The flight
- Flight plan: none
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number CEN21LA040.