Near midair collision at non tower airport with opposite direction takeoff.

Attributes
ACN	306999
Time
Date	199506
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : pga
State Reference	AZ
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : atl
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff
Flight Plan	None
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial climbout : takeoff
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 25 flight time total : 630 flight time type : 60
ASRS Report	306999
Person 2
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	conflict : nmac conflict : ground critical incursion : runway non adherence : published procedure other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	none taken : insufficient time
Consequence	Other
Miss Distance	horizontal : 0 vertical : 200
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

In process of departing page, az, I checked traffic, announced on 122.8 that I was departing on runway 33, and moved into position for takeoff. I could not see the opposite end of the runway distinctly. Just as I started to apply power another aircraft passed overhead, departing on runway 15. Prior to my entering the runway, there had been numerous operations on runway 33, all announced by pilots on 122.8, which is the CTAF. After a garbled transmission a min or so prior to my entry onto the runway, I heard a response from an airborne aircraft something like 'aw come on fellow everybody's using runway 33.' I assumed that the garbled transmission I heard must have come from distant airborne traffic. At the time of the incident another aircraft (a baron, I think) was turning from downwind to base for landing on runway 33, and had clearly announced his intentions. He may have been the one who objected to the runway 15 departure.

Original NASA ASRS Text

Title: NMAC AT NON TWR ARPT WITH OPPOSITE DIRECTION TKOF.

Narrative: IN PROCESS OF DEPARTING PAGE, AZ, I CHKED TFC, ANNOUNCED ON 122.8 THAT I WAS DEPARTING ON RWY 33, AND MOVED INTO POS FOR TKOF. I COULD NOT SEE THE OPPOSITE END OF THE RWY DISTINCTLY. JUST AS I STARTED TO APPLY PWR ANOTHER ACFT PASSED OVERHEAD, DEPARTING ON RWY 15. PRIOR TO MY ENTERING THE RWY, THERE HAD BEEN NUMEROUS OPS ON RWY 33, ALL ANNOUNCED BY PLTS ON 122.8, WHICH IS THE CTAF. AFTER A GARBLED XMISSION A MIN OR SO PRIOR TO MY ENTRY ONTO THE RWY, I HEARD A RESPONSE FROM AN AIRBORNE ACFT SOMETHING LIKE 'AW COME ON FELLOW EVERYBODY'S USING RWY 33.' I ASSUMED THAT THE GARBLED XMISSION I HEARD MUST HAVE COME FROM DISTANT AIRBORNE TFC. AT THE TIME OF THE INCIDENT ANOTHER ACFT (A BARON, I THINK) WAS TURNING FROM DOWNWIND TO BASE FOR LNDG ON RWY 33, AND HAD CLRLY ANNOUNCED HIS INTENTIONS. HE MAY HAVE BEEN THE ONE WHO OBJECTED TO THE RWY 15 DEP.

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.