# Accident 19971007030452A: Piper PA32260, Robbins, NC, October 7, 1997

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 7, 1997, 13:37 local time
- Place: Robbins, NC
- Damage: Destroyed
- Collision: Midair collision, second aircraft
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 35.4304° N, 79.5796° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=35.4304&lon=-79.5796&mi=10
- Aircraft: N3940W, a cancelled registration (https://openairdocs.org/deregistered/N3940W-1999-04-06) (OpenAirDocs)
- Registry model: Piper PA-32-260 (registry code 7103206, https://openairdocs.org/model/piper-pa-32-260) (OpenAirDocs)
- Reported make and model: PIPER PA32260
- Reported engine: LYC O540E4B5
- People aboard: 2
- Fatal injuries: 2
- Pilot flight hours: 351 total, 93 in this make and model, 22 in the last 90 days
- NTSB investigation: [NTSB MIA98FA007](https://openairdocs.org/ntsb/MIA98FA007) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19971007030452A

## Narrative

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

COLLIDED WITH IFR TRAFFIC AT VFR CRUISE LEVEL TRAFFIC N2050W THAT HAD JUST GOT IFR. ATC FAILED SEE TRAFFIC PA32. (.4)THE PILOT OF BEECH 35, N2050W, PHONED THE LEESBURG AUTOMATED FLIGHT SERVICE STATION (AFSS) TO FILE A ROUND TRIP IFR FLIGHT PLAN, BUT THE BRIEFING SPECIALIST INADVERTENTLY INPUTTED THE DEPARTURE TIME AS 1130 UTC INSTEAD OF 1530 UTC (1130 LOCAL). THE BEECH FLIGHT DEPARTED VFR, AND THE PILOT ATTEMPTED TO OBTAIN AN IFR CLEARANCE, BUT THE CONTROLLER ADVISED HIM THAT THERE WAS NO IFR FLIGHT PLAN IN THE SYSTEM. THE PILOT ADVISED THE CONTROLLER THAT HE WOULD PROCEED VFR. WHILE EN ROUTE, THE BEECH WAS ON A NORTH-NORTHWESTERLY COURSE, WHEN IT BEGAN TO CONVERGE WITH PIPER PA-32, N3940W, THAT WAS ON A EAST-NORTHEASTERLY COURSE AT ABOUT THE SAME ALTITUDE. AT ABOUT THAT TIME, THE BEECH PILOT CONTACTED AN ATC FACILITY AND STATED THAT HIS FLIGHT WAS LEVEL AT 5,500 FEET. HE WAS GIVEN A DISCRETE TRANSPONDER CODE TO SQUAWK, AND THE PILOT COMPLIED. THE CONTROLLER IMMEDIATELY ADVISED THE PILOT THAT TRAFFIC WAS OFF TO HIS LEFT, BUT THERE WAS NO ACKNOWLEDGEMENT. BOTH AIRPLANES CRASHED INTO A RURAL AREA. AN INVESTIGATION REVEALED THE NOSE LANDING GEAR OF                                      PIPER COLLIDED WITH THE LEFT WING TIP OF THE BEECH. REVIEW OF THE FAR'S REVEALED THAT WHILE FLYING VFR BETWEEN 180 AND 359 DEGREES MAGNETIC COURSE, ABOVE 3000 FEET ABOVE GROUND LEVEL (AGL), THE PILOT SHOULD FLY AT EVEN THOUSAND FEET ALTITUDE PLUS 500 FEET.  VFR FLIGHT BETWEEN 0 AND 179 DEGREES, ABOVE 3000 FEET AGL, SHOULD BE AT ODD THOUSANDS PLUS 500 FEET.               (-23) SEE NARRATIVE #MIA98FA007B.

## Other aircraft in the event

- N2050W, Beech 35C33A: [Accident 19971007030451A](https://openairdocs.org/incident/19971007030451A)

## 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 MIA98FA007](https://openairdocs.org/ntsb/MIA98FA007), Oct 7, 1997: Piper PA-32-260 (N3940W), Robbins, NC, destroyed, 3 fatal. Probable cause: failure of the pilots in both aircraft to see-and-avoid each other's airplane (inadequate visual lookout), and failure of the Beech pilot to operate his airplane at a correct Visual Flight Rules…

## Other reports on N3940W (1)

Matched to the same aircraft by N-number and date.

- [Accident 19781118044459A](https://openairdocs.org/incident/19781118044459A), Nov 18, 1978: Piper PA32260 (N3940W), South Boston, VA, Substantial damage. Plt stated preoccupied with selecting safe lndg area rather than arting eng.

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.