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/YEDCPAAEUX53AK6N2DM4GREOGHFGFU5P/",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/",
    "message_id": "8de4dfe9-af75-43e4-b60d-3cc135331189@nasanexmsp01.na.qualcomm.com",
    "message_id_hash": "YEDCPAAEUX53AK6N2DM4GREOGHFGFU5P",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/HBSEA5YT75AOQMTR5M3IXQ4R6OG7PCHR/",
    "sender": {
        "address": "antonio (a) qualcomm.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Franklin Antonio",
    "subject": "[amsat-bb] Re: Satellites in collision",
    "date": "2009-02-13T11:48:45Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/DB6I6O3OBHCDL25THS5G47MXM4DVTAHO/",
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "At 03:27 AM 2/13/2009, Rich Dailey (gmail) wrote:\n>*If* the controllers of the Iridium satellite could alter it's orbit \n>slightly,  how would that have affected their bottom line as far as \n>the operation of the entire constellation?  Was it cheaper to just \n>let them crash,  and then apologize to the space community afterward?\n\nCommercial satellites are horribly expensive.  Almost anything would \nhave been preferable to just letting them crash.\n\nThey do station-keeping.  (If they didn't, the things wouldn't stay \nnicely spaced in their constellation, and the Iridium system design \ndepends on keeping the satellites nicely spaced.)  Therefore they \nhave the ability to make small orbit changes.  I believe that with \nenough advance notice an adjustment could have been done with a very \nsmall amount of fuel.  One can only conclude that they did not have \nadvance notice.  I doubt we'll ever learn the inside story.\n\nI'll bet they start up an effort to predict future collision \npossibilities pronto.\n",
    "attachments": []
}