Narrative:

I and another aircraft (a C172) were in the traffic pattern for runway 36 at waterbury-oxford airport (oxc) practicing night lndgs. The standard calm wind runway at oxc is runway 36 with left traffic. On my last circuit of the traffic pattern, while on short final (about 1/2 mi and 500 ft AGL), with the C172 behind me on base leg, I observed landing lights in the distance. The lights appeared to be about 3 mi north. To this point, I received no communications from the inbound aircraft on the CTAF, but was hearing the C172 clearly. I recognized the light pattern as that of a turbine aircraft, of which there are many based at oxc. As I approached the runway threshold I became concerned that the turbine traffic was going to land on the opposing runway 18. Upon touching down, I maneuvered to the far right side of the runway should the jet actually land. A go around was considered, but not executed due to my low altitude, the possibility of wake turbulence from the turbine aircraft and numerous hangars and terrain east of the runway. After approximately 500 ft of rollout, I observed the turbine aircraft making a right turn to the west at approximately 800 ft AGL. During the entire incident, my landing lights were on. To this point, I had not heard one single radio transmission from the turbine aircraft. I know my radio was working because I talked to the tower ground controller 2 to 3 mins before the tower closed. I also heard the tower sign off. My aircraft and the C172 were making the standard location calls to area traffic for nearly 30 mins prior to the incident. I believe the cause of this incident to be lack of communication on the part of the turbine aircraft and lack of respect to understanding oxc procedures. Another possible explanation could be an approach to oxc was begun while intending to land elsewhere. While securing my plane, I was very irritated with the fact that turbine aircraft based at oxc have done this in the past. To add insult, another turbine aircraft departed runway 18 against the calm wind procedures that also happen to be there for noise abatement. Guess who gets the angry neighbors calling? Hint: not the jet jockeys. At this point, I was really aggravated and obtained the registration numbers of both the incident and departing aircraft. The suspect aircraft landed approximately 10 mins after turning west. The establishment of an operating control tower has eliminated many of these incidents, but is of no use after hours. I strongly urge the FAA/FSDO to look into turbine aircraft operations at oxc. Maybe the tower hours need to be extended until XA00 local.

Related reports:

Google
 

Original NASA ASRS Text

Title: C150 PLT CONDUCTING NIGHT OPS AT OXC TAKES PRECAUTIONARY EVASIVE ACTION IN LNDG ROLL FOR A GLF4 EXECUTING AN OPPOSITE DIRECTION GAR. PLT IRRITATED BECAUSE GLF4 HAS NOT MADE STANDARD CTAF APCH RPTS.

Narrative: I AND ANOTHER ACFT (A C172) WERE IN THE TFC PATTERN FOR RWY 36 AT WATERBURY-OXFORD ARPT (OXC) PRACTICING NIGHT LNDGS. THE STANDARD CALM WIND RWY AT OXC IS RWY 36 WITH L TFC. ON MY LAST CIRCUIT OF THE TFC PATTERN, WHILE ON SHORT FINAL (ABOUT 1/2 MI AND 500 FT AGL), WITH THE C172 BEHIND ME ON BASE LEG, I OBSERVED LNDG LIGHTS IN THE DISTANCE. THE LIGHTS APPEARED TO BE ABOUT 3 MI N. TO THIS POINT, I RECEIVED NO COMS FROM THE INBOUND ACFT ON THE CTAF, BUT WAS HEARING THE C172 CLRLY. I RECOGNIZED THE LIGHT PATTERN AS THAT OF A TURBINE ACFT, OF WHICH THERE ARE MANY BASED AT OXC. AS I APCHED THE RWY THRESHOLD I BECAME CONCERNED THAT THE TURBINE TFC WAS GOING TO LAND ON THE OPPOSING RWY 18. UPON TOUCHING DOWN, I MANEUVERED TO THE FAR R SIDE OF THE RWY SHOULD THE JET ACTUALLY LAND. A GAR WAS CONSIDERED, BUT NOT EXECUTED DUE TO MY LOW ALT, THE POSSIBILITY OF WAKE TURB FROM THE TURBINE ACFT AND NUMEROUS HANGARS AND TERRAIN E OF THE RWY. AFTER APPROX 500 FT OF ROLLOUT, I OBSERVED THE TURBINE ACFT MAKING A R TURN TO THE W AT APPROX 800 FT AGL. DURING THE ENTIRE INCIDENT, MY LNDG LIGHTS WERE ON. TO THIS POINT, I HAD NOT HEARD ONE SINGLE RADIO XMISSION FROM THE TURBINE ACFT. I KNOW MY RADIO WAS WORKING BECAUSE I TALKED TO THE TWR GND CTLR 2 TO 3 MINS BEFORE THE TWR CLOSED. I ALSO HEARD THE TWR SIGN OFF. MY ACFT AND THE C172 WERE MAKING THE STANDARD LOCATION CALLS TO AREA TFC FOR NEARLY 30 MINS PRIOR TO THE INCIDENT. I BELIEVE THE CAUSE OF THIS INCIDENT TO BE LACK OF COM ON THE PART OF THE TURBINE ACFT AND LACK OF RESPECT TO UNDERSTANDING OXC PROCS. ANOTHER POSSIBLE EXPLANATION COULD BE AN APCH TO OXC WAS BEGUN WHILE INTENDING TO LAND ELSEWHERE. WHILE SECURING MY PLANE, I WAS VERY IRRITATED WITH THE FACT THAT TURBINE ACFT BASED AT OXC HAVE DONE THIS IN THE PAST. TO ADD INSULT, ANOTHER TURBINE ACFT DEPARTED RWY 18 AGAINST THE CALM WIND PROCS THAT ALSO HAPPEN TO BE THERE FOR NOISE ABATEMENT. GUESS WHO GETS THE ANGRY NEIGHBORS CALLING? HINT: NOT THE JET JOCKEYS. AT THIS POINT, I WAS REALLY AGGRAVATED AND OBTAINED THE REGISTRATION NUMBERS OF BOTH THE INCIDENT AND DEPARTING ACFT. THE SUSPECT ACFT LANDED APPROX 10 MINS AFTER TURNING W. THE ESTABLISHMENT OF AN OPERATING CTL TWR HAS ELIMINATED MANY OF THESE INCIDENTS, BUT IS OF NO USE AFTER HRS. I STRONGLY URGE THE FAA/FSDO TO LOOK INTO TURBINE ACFT OPS AT OXC. MAYBE THE TWR HRS NEED TO BE EXTENDED UNTIL XA00 LCL.

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.