A C172 CFI on a night operation has a potential conflict with unknown landing traffic on runway 20 d...

Attributes
ACN	537699
Time
Date	200202
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : tpl.airport
State Reference	TX
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff
Flight Plan	None
Aircraft 2
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : multi engine pilot : cfi pilot : commercial
Experience	flight time last 90 days : 31 flight time total : 1037 flight time type : 636
ASRS Report	537699
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : far non adherence : published procedure other anomaly other other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	other
Miss Distance	horizontal : 4000 vertical : 500
Supplementary
Problem Areas	Airport Environmental Factor Flight Crew Human Performance
Primary Problem	Environmental Factor
Situations
Airport	other physical facility procedure or policy : tpl.airport

Narrative:

On the evening of feb/mon/02, I was scheduled for a night currency flight. After startup and listening to AWOS, I switched to the temple CTAF (123.00) and announced that I was taxiing to runway 15. During runup, I heard a couple of aircraft announcing their position at georgetown airport (gtu, CTAF also 123.00) but heard no traffic calls for temple. During runup, I observed no aircraft in the pattern, saw no aircraft land, and saw no aircraft lights on the runways or txwys. I announced that I was 'taking runway 15 for left closed traffic' and, after a visual check and receiving no answer on the radio, made a normal takeoff. As I reached about 500 ft AGL, someone came on the radio and said 'aircraft that just took off from georgetown, you're not too bright.' I announced my crosswind turn, and the same voice said 'cessna at temple, did you see us on the active?' I replied that if he was calling me that no, I had not seen or heard another aircraft. The other pilot replied 'why didn't you announce your takeoff?' I replied that I had indeed announced that I was taking runway 15 for left closed traffic, and had heard no answer and had seen no aircraft. After announcing my downwind turn, the other pilot called that he was 'on taxiway C' and 'regaining his composure.' factors: 1) night. 2) probability that the other pilot was calling 'georgetown traffic' rather than 'temple traffic.' 3) possibility that the other aircraft had landed on runway 20 and was out of my sight (runway 15 and runway 20 intersect). 4) other pilot's failure to use proper radio procedures, hear my call that I was taking runway 15 and inform me he was out there. 5) my failure to see the other aircraft. This occurrence disturbs me as a pilot and CFI. Safety is my career, my job and my responsibility. If an aircraft was on my runway or an intersecting runway, it was my duty to see him, regardless of the radio. I consider myself a safe and vigilant pilot, but I intend to redouble my efforts, particularly at non-twred fields with multiple runways.

Original NASA ASRS Text

Title: A C172 CFI ON A NIGHT OP HAS A POTENTIAL CONFLICT WITH UNKNOWN LNDG TFC ON RWY 20 DURING HIS VMC DEP FROM RWY 15 AT TPL, TX.

Narrative: ON THE EVENING OF FEB/MON/02, I WAS SCHEDULED FOR A NIGHT CURRENCY FLT. AFTER STARTUP AND LISTENING TO AWOS, I SWITCHED TO THE TEMPLE CTAF (123.00) AND ANNOUNCED THAT I WAS TAXIING TO RWY 15. DURING RUNUP, I HEARD A COUPLE OF ACFT ANNOUNCING THEIR POS AT GEORGETOWN ARPT (GTU, CTAF ALSO 123.00) BUT HEARD NO TFC CALLS FOR TEMPLE. DURING RUNUP, I OBSERVED NO ACFT IN THE PATTERN, SAW NO ACFT LAND, AND SAW NO ACFT LIGHTS ON THE RWYS OR TXWYS. I ANNOUNCED THAT I WAS 'TAKING RWY 15 FOR L CLOSED TFC' AND, AFTER A VISUAL CHK AND RECEIVING NO ANSWER ON THE RADIO, MADE A NORMAL TKOF. AS I REACHED ABOUT 500 FT AGL, SOMEONE CAME ON THE RADIO AND SAID 'ACFT THAT JUST TOOK OFF FROM GEORGETOWN, YOU'RE NOT TOO BRIGHT.' I ANNOUNCED MY XWIND TURN, AND THE SAME VOICE SAID 'CESSNA AT TEMPLE, DID YOU SEE US ON THE ACTIVE?' I REPLIED THAT IF HE WAS CALLING ME THAT NO, I HAD NOT SEEN OR HEARD ANOTHER ACFT. THE OTHER PLT REPLIED 'WHY DIDN'T YOU ANNOUNCE YOUR TKOF?' I REPLIED THAT I HAD INDEED ANNOUNCED THAT I WAS TAKING RWY 15 FOR L CLOSED TFC, AND HAD HEARD NO ANSWER AND HAD SEEN NO ACFT. AFTER ANNOUNCING MY DOWNWIND TURN, THE OTHER PLT CALLED THAT HE WAS 'ON TXWY C' AND 'REGAINING HIS COMPOSURE.' FACTORS: 1) NIGHT. 2) PROBABILITY THAT THE OTHER PLT WAS CALLING 'GEORGETOWN TFC' RATHER THAN 'TEMPLE TFC.' 3) POSSIBILITY THAT THE OTHER ACFT HAD LANDED ON RWY 20 AND WAS OUT OF MY SIGHT (RWY 15 AND RWY 20 INTERSECT). 4) OTHER PLT'S FAILURE TO USE PROPER RADIO PROCS, HEAR MY CALL THAT I WAS TAKING RWY 15 AND INFORM ME HE WAS OUT THERE. 5) MY FAILURE TO SEE THE OTHER ACFT. THIS OCCURRENCE DISTURBS ME AS A PLT AND CFI. SAFETY IS MY CAREER, MY JOB AND MY RESPONSIBILITY. IF AN ACFT WAS ON MY RWY OR AN INTERSECTING RWY, IT WAS MY DUTY TO SEE HIM, REGARDLESS OF THE RADIO. I CONSIDER MYSELF A SAFE AND VIGILANT PLT, BUT I INTEND TO REDOUBLE MY EFFORTS, PARTICULARLY AT NON-TWRED FIELDS WITH MULTIPLE RWYS.

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.

A C172 CFI on a night operation has a potential conflict with unknown landing traffic on runway 20 during his VMC departure from runway 15 at tpl, tx.