Pilot in a BE36 taxied out for departure at olu, an uncontrolled airport. Using CTAF procedures, the pilot announced his departure and did not hear any other calls. At lift-off the pilot noticed an aircraft landing on the opposite end. He made an immediate right turn to avoid a collision. The pilot then noticed he was on the incorrect airport frequency.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	408364
Time
Date	199807
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : olu
State Reference	NE
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Bonanza 36
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	landing other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 60 flight time total : 2800 flight time type : 1600
ASRS Report	408364
Person 2
Function	flight crew : single pilot
Events
Anomaly	conflict : ground less severe other anomaly other other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action none taken : unable
Consequence	Other
Miss Distance	horizontal : 3000
Supplementary
Primary Problem	Flight Crew Human Performance

Narrative:

We taxied out from the airport for departure from the small uncontrolled airport. The wind was calm. Before entering the runway a radio call was made to announce entry to the runway, no radio calls were heard from others. At rotation, another airplane coming in for landing was noted at the distant approach end to the runway. The airplane was rolling and in rotation so that a stop at that time would have yielded undesired effects and would have probably caused a crash. Our airplane rolled right and out of the runway environment. At this time it was noted that the wrong unicom frequency was dialed in on the radio. The correct frequency was not used and yielded the missed call of the other traffic in the pattern. Approximately distances were 3000 ft or more laterally. The error herein was with having the incorrect frequency dialed in on the communication side of the radio stack.

Original NASA ASRS Text

Title: PLT IN A BE36 TAXIED OUT FOR DEP AT OLU, AN UNCTLED ARPT. USING CTAF PROCS, THE PLT ANNOUNCED HIS DEP AND DID NOT HEAR ANY OTHER CALLS. AT LIFT-OFF THE PLT NOTICED AN ACFT LNDG ON THE OPPOSITE END. HE MADE AN IMMEDIATE R TURN TO AVOID A COLLISION. THE PLT THEN NOTICED HE WAS ON THE INCORRECT ARPT FREQ.

Narrative: WE TAXIED OUT FROM THE ARPT FOR DEP FROM THE SMALL UNCTLED ARPT. THE WIND WAS CALM. BEFORE ENTERING THE RWY A RADIO CALL WAS MADE TO ANNOUNCE ENTRY TO THE RWY, NO RADIO CALLS WERE HEARD FROM OTHERS. AT ROTATION, ANOTHER AIRPLANE COMING IN FOR LNDG WAS NOTED AT THE DISTANT APCH END TO THE RWY. THE AIRPLANE WAS ROLLING AND IN ROTATION SO THAT A STOP AT THAT TIME WOULD HAVE YIELDED UNDESIRED EFFECTS AND WOULD HAVE PROBABLY CAUSED A CRASH. OUR AIRPLANE ROLLED R AND OUT OF THE RWY ENVIRONMENT. AT THIS TIME IT WAS NOTED THAT THE WRONG UNICOM FREQ WAS DIALED IN ON THE RADIO. THE CORRECT FREQ WAS NOT USED AND YIELDED THE MISSED CALL OF THE OTHER TFC IN THE PATTERN. APPROX DISTANCES WERE 3000 FT OR MORE LATERALLY. THE ERROR HEREIN WAS WITH HAVING THE INCORRECT FREQ DIALED IN ON THE COM SIDE OF THE RADIO STACK.

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.