Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/AWDR37QSKX5RBMNAMFWS2WNJODEHGUAE/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "AWDR37QSKX5RBMNAMFWS2WNJODEHGUAE",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/AWDR37QSKX5RBMNAMFWS2WNJODEHGUAE/?format=api",
    "sender": {
        "address": "amsat-bb (a) wd9ewk.net",
        "mailman_id": "21664df01bef4757931b7cdb42a9e768",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/21664df01bef4757931b7cdb42a9e768/emails/?format=api"
    },
    "sender_name": "Patrick STODDARD (WD9EWK/VA7EWK)",
    "subject": "[amsat-bb]  WD9EWK from DM23vx/DM24va today",
    "date": "2009-09-20T06:15:45Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Hi!\n\nThis was a good day out in western Arizona.  I worked 6 different\npasses from the DM23/DM24 grid boundary (two on each of the 3 FM\nsatellites), scouted out another location closer to the Colorado \nRiver still in Arizona for this grid boundary, and logged a total \nof 60 QSOs with stations from central Mexico to western Canada and \nall across the USA.  \n\nThe spot I stopped at was approximately 11 miles/17.7km southeast\nof Parker AZ, north of the intersection of Arizona routes 72 and\n95 in La Paz County.  The coordinates are 34 0.00 N 114 12.925 W \n(this should work for Google Earth or Google Maps).  I had parked\naway from those two state highways on the side of the paved road \nrunning north across railroad tracks to a dead end, thinking I \nwould be out of the way and not attract attention from the law \nenforcement.  After my recent experience at DM31 near the Mexican \nborder 2 weekends ago (a couple of encounters with US Border Patrol \nagents), I should not have been surprised to see a state trooper \npay me a visit this afternoon.  \n\nI left Phoenix around 9am (1600 UTC), and had lots of time to make\nthe drive out to that spot.  Instead of taking a direct route to \nthere, which would have taken about 2.5 hours, I went a little \nfurther west and drove through the Colorado River Indian Reservation\nalong the east side of the Colorado River.  There was another spot\non the DM23/DM24 boundary I could have worked from, without returning\nto where I stopped last year and worked from this boundary.  After\nstopping for fuel and lunch, I went out to the spot I wanted to work\nfrom.  It took a few minutes to get the GPS reading to show 34 \ndegrees North, but once that was done I waited for the first AO-27\npass at 2051 UTC.\n\nThe first AO-27 pass to the east is usually a good one to work \nstations all over North America.  It was a good one once again,\nexcept for a brief interruption.  I was able to work the first \n2 minutes or so, before an Arizona state trooper stopped by and \nasked if I was having car problems.  Apparently someone driving\nalong one of those two state highways called the highway patrol\nto report my \"breakdown\".  Once I told the trooper I didn't have\na breakdown and that I was working the radio away from civilization\nout there, he drove away - and I resumed working stations.  A\ntotal of 16 stations were worked in about 6 of the 7 minutes on \nthat pass.  \n\nBefore the second AO-27 pass, I drove back to Parker to get some \nsnacks and take pictures at the Colorado River.  The western AO-27\npass at 2232 UTC brought 6 more QSOs.  Unfortunately, this pass was \ninterrupted by an Echolink node somewhere in the western US using \n145.850 MHz as its frequency.  I never heard the node ID itself, \nbut did hear one call of the station using the node.  I have my \nrecording from this pass and the others I worked out there, so I \ncan go back and get the call I heard and hope that the ham has an \ne-mail address.  Maybe that ham will tell me which Echolink node \nhe was using at that time.  \n\nA few minutes after that AO-27 pass, I had a shallow northeastern \nSO-50 pass at 2252 UTC, with a maximum elevation of  6 degrees.  I\nworked 7 stations in 5 minutes on that pass, a nice surprise.  Then\nI had the first of the AO-51 passes at 2333 UTC, a 12-degree pass \nto the east.  Fifteen QSOs logged, with stations in Mexico and all \nover the US.  \n\nThe last two passes, an SO-50 pass at 0028 UTC followed by an \nAO-51 pass at 0111 UTC, had 8 QSOs each.  By the time the AO-51\npass wrapped up, I disassembled my station and drove back home.  \nFor a trip that I didn't give a lot of advance notice about, \nand having worked from DM23/DM24 last year, this turned out to\nbe a good day.  I know I worked some calls for the first time \ntoday, and hopefully there will be a second QSO with them when\nI'm operating in or around Phoenix in the near future.  \n\nIf anyone wants a QSL card for a QSO - or QSOs - made with \nWD9EWK out in DM23/DM24, please e-mail me directly with the \ndetails of each QSO.  If you're in the log, I'll send you a\ncard.  No need to send me a QSL card or SASE.  I will need\nto make new QSL cards for this stop, since my previous trip\nto the DM23/DM24 boundary was in California.  I hope to do\nthat in the coming week.  \n\nThanks to everyone who showed up and worked me from out there\nin western Arizona.  73!\n\n\n\n\nPatrick WD9EWK/VA7EWK\nhttp://www.wd9ewk.net/\n\n\n",
    "attachments": []
}