Near midair collision between 2 small aircraft sel going same way and altitude.

Attributes
ACN	286238
Time
Date	199410
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : ont
State Reference	CA
Altitude	msl bound lower : 7500 msl bound upper : 7500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : ont
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	cruise other cruise other
Route In Use	enroute : on vectors
Flight Plan	VFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 20 flight time total : 150 flight time type : 150
ASRS Report	286238
Person 2
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	conflict : nmac other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : took evasive action other
Consequence	Other
Miss Distance	horizontal : 300 vertical : 20
Supplementary
Primary Problem	Flight Crew Human Performance

Narrative:

We were eastbound to psp, 7500 ft, flight following by ontario. ATC vectored us to 180 degrees for traffic on an alert. We complied. We tried to locate the traffic we were vectored from, but no joy. 2-3 mins later we suddenly saw an identical type plane (PA-28) on a collision course from our 3 O'clock evading to his left (our rear). We tried to contact ATC to inform him of the event and warn him of the heavy traffic headed to psp, but his radio traffic was too heavy and he didn't acknowledge. We therefore decided to turn back to our original heading so that we would not be perpendicular to the heavy psp bound traffic. Suggestion: when known heavy traffic events occur, establish an ATC protocol to keep traffic flying in the same direction.

Original NASA ASRS Text

Title: NMAC BTWN 2 SMA SEL GOING SAME WAY AND ALT.

Narrative: WE WERE EBOUND TO PSP, 7500 FT, FLT FOLLOWING BY ONTARIO. ATC VECTORED US TO 180 DEGS FOR TFC ON AN ALERT. WE COMPLIED. WE TRIED TO LOCATE THE TFC WE WERE VECTORED FROM, BUT NO JOY. 2-3 MINS LATER WE SUDDENLY SAW AN IDENTICAL TYPE PLANE (PA-28) ON A COLLISION COURSE FROM OUR 3 O'CLOCK EVADING TO HIS L (OUR REAR). WE TRIED TO CONTACT ATC TO INFORM HIM OF THE EVENT AND WARN HIM OF THE HVY TFC HEADED TO PSP, BUT HIS RADIO TFC WAS TOO HVY AND HE DIDN'T ACKNOWLEDGE. WE THEREFORE DECIDED TO TURN BACK TO OUR ORIGINAL HDG SO THAT WE WOULD NOT BE PERPENDICULAR TO THE HVY PSP BOUND TFC. SUGGESTION: WHEN KNOWN HVY TFC EVENTS OCCUR, ESTABLISH AN ATC PROTOCOL TO KEEP TFC FLYING IN THE SAME DIRECTION.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.