Aircraft X and aircraft Y land on the opposite ends of the runway at the same time.

Attributes
ACN	488924
Time
Date	200010
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : mjx.airport
State Reference	NJ
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : mco.tracon
Operator	general aviation : personal
Make Model Name	Cardinal 177/177RG
Operating Under FAR Part	Part 91
Flight Phase	landing : roll
Route In Use	approach : traffic pattern arrival : vfr
Flight Plan	None
Aircraft 2
Make Model Name	Piper Single Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	landing : roll
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 10 flight time total : 285 flight time type : 50
Person 2
Function	flight crew : single pilot
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Miss Distance	horizontal : 4000 vertical : 0
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

The AWOS broadcast gave winds favoring runway 6. The CTAF was so crowded that transmissions were impossible to understand. The windsock was showing wind direction variable, but I think still favoring runway 6. I made blind calls on downwind, base and final for runway 6 and heard no other traffic. I landed, made the first turnoff and then saw a tripacer that had landed on 24 turning off the far end of the runway. My a/C was showing beacon and strobes, was no lights on the piper. Discussion with fuel personnel revealed what they saw not an unusual occurrence at mjx and in fact happened again during the approximately 30 minutes I was there. Suggested corrective actions: check calibration of AWOS wind sensor. Installation of wind tee to indicate active runway. Change CTAF to less congested frequency. Make additional frequency available for CTAF. Callback conversation revealed the following information: reporter did not reveal any new information.

Original NASA ASRS Text

Title: ACFT X AND ACFT Y LAND ON THE OPPOSITE ENDS OF THE RWY AT THE SAME TIME.

Narrative: THE AWOS BROADCAST GAVE WINDS FAVORING RWY 6. THE CTAF WAS SO CROWDED THAT TRANSMISSIONS WERE IMPOSSIBLE TO UNDERSTAND. THE WINDSOCK WAS SHOWING WIND DIRECTION VARIABLE, BUT I THINK STILL FAVORING RWY 6. I MADE BLIND CALLS ON DOWNWIND, BASE AND FINAL FOR RWY 6 AND HEARD NO OTHER TRAFFIC. I LANDED, MADE THE FIRST TURNOFF AND THEN SAW A TRIPACER THAT HAD LANDED ON 24 TURNING OFF THE FAR END OF THE RWY. MY A/C WAS SHOWING BEACON AND STROBES, WAS NO LIGHTS ON THE PIPER. DISCUSSION WITH FUEL PERSONNEL REVEALED WHAT THEY SAW NOT AN UNUSUAL OCCURRENCE AT MJX AND IN FACT HAPPENED AGAIN DURING THE APPROX 30 MINUTES I WAS THERE. SUGGESTED CORRECTIVE ACTIONS: CHECK CALIBRATION OF AWOS WIND SENSOR. INSTALLATION OF WIND TEE TO INDICATE ACTIVE RWY. CHANGE CTAF TO LESS CONGESTED FREQUENCY. MAKE ADDITIONAL FREQUENCY AVAILABLE FOR CTAF. CALLBACK CONVERSATION REVEALED THE FOLLOWING INFO: RPTR DID NOT REVEAL ANY NEW INFO.

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.