| SSN: | 122 |
| SFI: | 131 |
| A: | 9 |
| K: | 4 |

More than 80000 QSOs are now in the log ! Congratulations to the team and thanks all for calling. They are now fighting hard to get the 2000 QSO left for the RTTY World Record. We will cross fingers for them, please call !!
A new batch of pictures has been posted on www.PJ4C.com.
Hi
To be informed in time join the PJ4C 2012 mailing list.
Subscribe : f5nql@aol.com
73
Maurice, F5NQL,
KOP Team member,
Information by Internet mailing list for PJ4C 2012.
Muy buena noticia. Ojalá se acuerden de los sudakas y en algún momento apunte las antenas para SA y nos permitan hacer algún QSO con Bonaire.
Gracias.
Javier
Good luck, guys!
Hope for you great effort for “top” band.
73!!!
Have a safe trip, hope to get you in log on 40m cw. Also pls learn om OZ1IKY to speak better french..hihi
rgds.
I don’t know who these obvious novice PJ4C expedition operators are, but someone needs to grab them, SHAKE them and have them read the DX CODE of CONDUCT for Expeditioners.
The UNNECESSARY confusion on the packet cluster with HK0NA posts has resulted from the miserable FAILURE of the PJ4C operators to make reasonable I.D. (in other words, SIGN THEIR #&^! CALLSIGN frequently).
There should be a COMPETENCY TEST required for Expedition operators.
Very, very, very poor Expedition operating by PJ4C resulting in UNNECESARY CONFUSION.
WAKE UP, YOU GUYS !!!
Rick, K6VVA
You MUST ID more often…You are causing mass confusion with HK0NA and also QRG on top of HK0NA posted frequencies…
ID ID ID…this is horrible practice.
I have worked PJ4C with no issue and they signed everytime with their callsign.
I saw what was spotted on the DX Cluster yesterday about PJ4C and people whining about it, but what I ask is this…..
Did you just take for granted this was HK0NA when it clearly wasn’t?
What made you think it was HK0NA to begin with?
It seems this problem is on CW because they’re are ID’ing quite fine on SSB.
Does HK0NA sound anything like PJ4C in CW??
To lame blame and say they are causing mass confusion is just ridiculous, listen first before you call and don’t assume that just because HK0NA uses that frequency and it’s posted on their website that it is actually them.
It’s always the Expeditioners fault isn’t it? Never the home operator
PJ4C is now on 14024 and they only ID when asked to and there is a great confusion on the cluster about who it is
14023.9 PJ4C 15-Jan-2012 1659Z UP 2
14024.0 PJ4C 15-Jan-2012 1659Z UP 2
14024.0 PJ4C 15-Jan-2012 1655Z Up 1,4
14024.0 PJ4C 15-Jan-2012 1654Z
14023.9 PJ4C 15-Jan-2012 1650Z Tnx 73 Wrked Up 5
14024.0 PJ4C 15-Jan-2012 1650Z not HK0NA my mistake !!!
14024.0 PJ4C 15-Jan-2012 1649Z NOT HK0NA !!!
14024.0 PJ4C 15-Jan-2012 1644Z up 5 got him! luv split :)
14024.0 HK0NA 15-Jan-2012 1653Z up 4.4 HK0-M
14024.0 HK0NA 15-Jan-2012 1649Z up 4.4
14024.0 HK0NA 15-Jan-2012 1629Z booming into MO up 4.4
14024.0 HK0NA 15-Jan-2012 1617Z QSX 14029.66
14024.0 HK0NA 15-Jan-2012 1616Z NOT HK0NA is PJ4C
14024.0 HK0NA 15-Jan-2012 1616Z It is NOT HK0NA, it´s PJ4C
14024.0 HK0NA 15-Jan-2012 1615Z qsx up up
14023.9 HK0NA 15-Jan-2012 1612Z 599 Sig in SW MO-Up 5.16
14024.0 HK0NA 15-Jan-2012 1603Z UP – Loudest so far!
14024.0 HK0NA 15-Jan-2012 1525Z ??ID qsx up 2
Problem was:
Not frequent enough ID’ing (but if you listened, you’d know pretty quickly who it was)
People who either DON’T listen or can’t copy cw except for 599 and their own call
People putting inaccurate spots on the cluster (a HUGE problem not only with PJ4C but in general)
People simply trusting a spot and not id’ing the station for themselves
and of course people who don’t shut up and listen. They’re so busy calling they wouldn’t even know if they were the ones being called.
The solution comes right back to the DX Code of Conduct. If DXpeditions followed it (identifying with nearly every call) and if those trying to work the DXpedition listened more than the transmitted, and exhibited the common courtesy of SHUTTING UP when some else is being called. things would be so much more enjoyable, and so many more stations would be worked.
I have worked PJ4C on 20 band slots so far – they are real professionals – I hear their callsign constantly – absolutely great DXpedition!
Keep up the great work and have fun!
hello all,
not easy to pile up one after 14 hours of travel, some are not accommodating,
30 000 qso but tonight, it’s not so bad …
it is important to play with the radio, it’s a pleasure
We are not professional, just friends who are here to please you.
thank you
f6jmt / pj4c bonaire
the problem is HK0NA
the expedition should not start before a specific day.
the operators do not meet our frequency!
it’s a shame,
we are looking for a solution to this problem.
73′s F6JMT / BONAIRE PJ4C
Wow, the confusion has disappeared, and I notice they are Id’ing every time. It’s amazing how much of an impact that can have, and really makes a strong case for this procedure.
Hola Bernard un abrazo para ti y por favor dale un saludos grande a Henri, Frank y a todos los muchachos que vi en Friedrichshafen
Realy nice DX Pedition with very good OP´s.
Thx for 2 new Bands.
Hope to get the QSL Card soon.
73´s OE7PGI
PJ4C – please avoid 3.772 to 3.778 between 0600 and 0900 UTC you are causing severe disruption to a number of long established (15 to 20 years) European nets – thankyou for your consideration in operating more carefully.
hi guys gud job and gud signals in NH. have worked you on several bands cw and phone.(why should others complain) tnx for being there. n1kjw
THESE MEN CERTAINLY ARE NO “JOHNNIE-COME-LATELYS” VY GUD OPS…THEY’LL TRY 3-4 TIMES TO GET A CALL CORRECT..73, GREG