C172 pilot aborts takeoff at avq when he realizes another C172 is departing in the opposite direction at a non twred airport.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	684333
Time
Date	200601
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : avq.airport
State Reference	AZ
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	ground : takeoff roll
Flight Plan	None
Aircraft 2
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	ground : takeoff roll
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	controller : radar controller : non radar pilot : cfi pilot : instrument pilot : commercial
Experience	controller non radar : 10 controller radar : 5 flight time last 90 days : 25 flight time total : 3800 flight time type : 200
ASRS Report	684333
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	conflict : ground critical other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : rejected takeoff
Supplementary
Problem Areas	Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

My aircraft was departing marana northwest regional airport at XA00 on jan/mon/05. We followed another C172 out to runway 30 for departure. Winds were out of the northwest at 10 KTS. The C172 pulled into a run-up area. We took runway 30 after I made an announcement we were taking runway 30 for a right crosswind departure. As we lined up on the centerline and applied full throttle; I looked down at the other end of the runway; there was a cessna departing runway 12. I applied my brakes and aborted the takeoff. (There was at least 2500 ft of separation.) I heard no radio calls. Then as he overflew us; I heard him speak saying 'is he on frequency?' I believe my radio was not on the proper frequency of 123.00. I believe at the time of takeoff the radio was set to 123.05. As I aborted my takeoff; I looked at the radio to change the frequency to 123.00. After this; I contacted the other cessna to advise him I had him in sight and I was aborting the takeoff. This event could have been avoided by verifying the proper radio frequency was set in the radio by myself and if the other pilot followed standard aim procedures of taking off into the wind.

Original NASA ASRS Text

Title: C172 PLT ABORTS TKOF AT AVQ WHEN HE REALIZES ANOTHER C172 IS DEPARTING IN THE OPPOSITE DIRECTION AT A NON TWRED ARPT.

Narrative: MY ACFT WAS DEPARTING MARANA NW REGIONAL ARPT AT XA00 ON JAN/MON/05. WE FOLLOWED ANOTHER C172 OUT TO RWY 30 FOR DEP. WINDS WERE OUT OF THE NW AT 10 KTS. THE C172 PULLED INTO A RUN-UP AREA. WE TOOK RWY 30 AFTER I MADE AN ANNOUNCEMENT WE WERE TAKING RWY 30 FOR A R XWIND DEP. AS WE LINED UP ON THE CTRLINE AND APPLIED FULL THROTTLE; I LOOKED DOWN AT THE OTHER END OF THE RWY; THERE WAS A CESSNA DEPARTING RWY 12. I APPLIED MY BRAKES AND ABORTED THE TKOF. (THERE WAS AT LEAST 2500 FT OF SEPARATION.) I HEARD NO RADIO CALLS. THEN AS HE OVERFLEW US; I HEARD HIM SPEAK SAYING 'IS HE ON FREQ?' I BELIEVE MY RADIO WAS NOT ON THE PROPER FREQ OF 123.00. I BELIEVE AT THE TIME OF TKOF THE RADIO WAS SET TO 123.05. AS I ABORTED MY TKOF; I LOOKED AT THE RADIO TO CHANGE THE FREQ TO 123.00. AFTER THIS; I CONTACTED THE OTHER CESSNA TO ADVISE HIM I HAD HIM IN SIGHT AND I WAS ABORTING THE TKOF. THIS EVENT COULD HAVE BEEN AVOIDED BY VERIFYING THE PROPER RADIO FREQ WAS SET IN THE RADIO BY MYSELF AND IF THE OTHER PLT FOLLOWED STANDARD AIM PROCS OF TAKING OFF INTO THE WIND.

Data retrieved from NASA's ASRS site as of January 2009 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.