{"id":31138,"date":"2026-08-18T08:18:12","date_gmt":"2026-08-18T12:18:12","guid":{"rendered":"https:\/\/ops.group\/blog\/?p=31138"},"modified":"2026-08-18T08:18:12","modified_gmt":"2026-08-18T12:18:12","slug":"spacex-starship-launches-major-airspace-disruption","status":"publish","type":"post","link":"https:\/\/ops.group\/blog\/spacex-starship-launches-major-airspace-disruption\/","title":{"rendered":"SpaceX Starship Launches: Major Airspace Disruption"},"content":{"rendered":"

On July 24 one of our members\u2019 aircraft – a medevac jet – departed MGGT\/Guatemala City bound for Florida. An hour or so later, while approaching the Belize\/Mexico border, ATC turned it around.<\/strong> SpaceX had just launched Starship Flight 13 from Boca Chica, Southern Texas, and the airspace ahead was closed. <\/strong>The aircraft returned to Guatemala, thankfully with no patient on board.<\/p>\n

The crew briefed normally, via ForeFlight, before departure. The key problem is that the system they were relying on wasn\u2019t built for what a major SpaceX launch actually does to the airspace.<\/strong><\/p>\n

\"\"<\/p>\n

It\u2019s not just one Notam. It\u2019s a wall.<\/h4>\n

A SpaceX Starship launch is a big deal.<\/strong> They\u2019re a test flight of the biggest, most powerful rocket ever built – the one SpaceX intends to eventually use for missions to the Moon and Mars. Bigger even than Apollo’s Saturn V that took Neil, Buzz and Michael to the lunar Sea of Tranquility back in 69′.<\/p>\n

They launch from a site called “Starbase,” on the southern tip of Texas\u00a0near Boca Chica Beach.<\/p>\n

Starship is actually two huge stages stacked together.<\/strong> The massive first stage does the heavy lifting off the pad and either flies itself back to the launch site or has a controlled splashdown in the ocean.<\/p>\n

Starship (the second stage) sits on top and continues into space along with whatever payload it\u2019s carrying.<\/p>\n

\"\"

SpaceX Starship<\/p><\/div>\n

But for aviation, the relevant bit isn\u2019t the spectacle. It\u2019s the debris and hazard footprint – which is huge.<\/strong><\/p>\n

It isn\u2019t just about closing a box of airspace around the pad. It involves a hazard corridor<\/strong> covering the first stage descent, splashdown, debris footprint i.e. the whole shebang.<\/p>\n

The corridor crosses several FIRs, and each FIR is responsible for publishing its own Notam for its slice of it. There\u2019s no single Notam that covers it all.<\/strong><\/p>\n

For this launch, Mexico<\/strong> published MMFR Notam B1467\/26. This described a polygon of airspace defined by no less than 14 lat\/longs referred to as \u2018Area B2′:<\/p>\n

B1467\/26 NOTAMR B1443\/26\r\nQ) MMFR\/QRDCA\/IV\/BO\/W\/000\/999\/\r\nA) MMFR\r\nB) 2607242245\r\nC) 2607300056\r\nD) DLY 2245-0056\r\nE) DANGEROUS AREA FOR LAUNCH OF ROCKET SPACEX STARSHIP FLT-13,\r\nLATERAL LIMIT AREA FORMED BY THE UNION OF THE FLW POINTS:\r\nAREA B2:\r\n2430N 09103W\r\n2430N 09052W\r\n2420N 09031W\r\n2312N 08804W\r\n2232N 08638W\r\n2212N 08600W\r\n2200N 08600W\r\n2117N 08538W\r\n2144N 08645W\r\n2216N 08832W\r\n2236N 08938W\r\n2303N 09114W\r\n2310N 09137W\r\n2430N 09103W\r\nFIR MEXICO (MMFR)\r\nF) SFC\r\nG) UNL<\/pre>\n
Have time to plot 14 coordinates from a single Notam? We don’t either<\/strong>. Here’s what this would look like if you did:<\/p>\n
\"\"<\/p>\n
Cuba<\/strong> published a separate Notam MUFH A2617\/26, restricting the use of certain waypoints in the Havana FIR – with a different take (re-routing traffic around specific points, rather than closing a defined chunk of airspace). That’s why it reads so differently to Mexico’s.<\/p>\n
A2617\/26 NOTAMR A2603\/26\r\nQ)MUFH\/QXXXX\/IV\/NBO\/E\/000\/999\/2107N07944W999\r\nA)MUFH B)2607232045 C)2607300100\r\nD)2045\/0100 DLY\r\nE)SOUTHBOUND TRAFFIC FROM KZMA, KZHU FIRS ENTERING MKJK FIR AND MMFR \r\nFIR, WILL BE ACCEPTED OVER:\r\n- SHARQ, CANOA, MAXIM UP TO 2150Z\r\n- FUNDI, TANIA, URSUS, BORDO, DYNAH, ENAMO UP TO 2135Z \r\n- ERRCA, GHANN, MEDKO, OVALU , BYGON UP TO 2100Z.\r\nWESTBOUND TRAFFIC COMING FROM THE EAST OF MUFH FIR, WILL BE \r\nACCEPTED OVER:\r\n- URLAM, MODIT, MEDKO ENTERING IN MMFR FIR UP TO 2045Z\r\nNORTHBOUND TRAFFIC FROM MHCC, MKJK FIRS , GRAND CAYMAN APP WILL BE \r\nACCEPTED UP TO 2235Z.\r\nTRAFFIC OVER GELOG WILL BE ACCEPTED UP TO 2245Z\r\nINCOMING TRAFFIC FROM MMID WILL BE ACCEPTED OVER:\r\n- ALURU L\/UL674 UP TO 2145Z\r\n- NUDAL, NUKAN, EMOSA, PEPSO UP TO 2235Z\r\nFOR AN EMERGENCY, AVAILABLE AIRPORTS: MUHA , MUVR, PLEASE READ \r\nNOTAMS A2480\/26 NOTAMR A2014\/26 , A2481\/26 NOTAMR A2015\/26 ( JET A1\r\nFUEL NOT AVAILABLE )\r\n-REASONS: SUPER HEAVY STARSHIP LAUNCH 13TH<\/pre>\n
Individually, each one reads like some kind of weird danger-area Notam. Only if you plot every FIR\u2019s Notams together do you see the the whole thing adds up to an east\/west wall blocking traffic spanning from Southern Texas, across the Gulf and Caribbean, all the way down to Barbados and the Lesser Antilles.<\/strong><\/p>\n
\"\"<\/p>\n
The problem of time<\/h4>\n
But it wasn\u2019t just the size of the disruption, but also time. The Mexican Notam wasn\u2019t issued until after they\u2019d pulled their ForeFlight briefing.<\/strong> Even Guatemalan ATC didn’t catch it when issuing the IFR clearance.<\/p>\n
There\u2019s currently no requirement for space launch Notams to go out any set number of hours in advance. They can and do get filed and re-filed reactively<\/em>.<\/strong><\/p>\n
Take the US for example. 14 CFR Part 417, Appendix B (which governs licensed launch operators’ hazard-area Notams) only requires the Notam to be effective thirty mins prior to flight.<\/strong> In practice, they’re usually visible 48 – 72hrs prior. But the key point here is that don’t have<\/span>\u00a0<\/em>to be.<\/p>\n
\"\"That’s also the nature of space flight. Launches slip constantly – minutes, hours, days.<\/strong> It\u2019s why we talk about launch “windows” and back-up days. Every slip means every affected FIR has to reissue its Notam, trying to stay ahead of a moving target and it get it into the system before the next crew pulls their briefing.<\/p>\n
In other words, there\u2019s plenty of wriggle room for something to slip through.<\/strong> This may well be what happened to the crew here, but we can’t say for certain. But it appears the system has gaps a normal briefing might not catch.<\/p>\n
Big space ambitions<\/h4>\n
Two things have crossed our desk recently suggest this problem isn’t going away and may get worse.<\/p>\n
First is that FAA is proposing<\/a> to streamline the approval process for commercial space ops.<\/strong> This will include greater flexibility to waive certain requirements when reviewing commercial space licences and permits. The number of operations each year is expected to double over the next decade. From an ops-perspective, airspace closures will become far more frequent<\/strong>. The FAA has published a handy SAFO<\/a> on this subject.<\/p>\n
Second, from SpaceX itself: In a recent earnings call, Elon Musk has floated the idea<\/a> of eventually flying Starship daily<\/em><\/span>.<\/p>\n
And the flight paths may change too.<\/strong> Right now, only the booster stage is landing back at the Boca Chica Starbase. The upper stage still splashes down in water. However, they will soon attempt to return that stage to the launch site too, in which case hazard and debris areas may begin to look like this:<\/p>\n
\"\"<\/b><\/p>\n
So how do we brief them?<\/h4>\n
The existing Notam system simply isn\u2019t designed to handle huge geographic areas which extend over multiple FIRs. We\u2019re not saying don\u2019t read them, but they can struggle to give you the full picture. What helps is live tracking.<\/strong><\/p>\n
And there are a few good places to find it. SpaceX publishes its own launch schedule<\/a>\u00a0which remains the primary source<\/strong> for launch schedules and status. They also share information on temporary flight restrictions associated with the Starbase launch site here<\/span><\/a>.<\/p>\n
\"\"<\/a>
SpaceX publishes a schedule of launches and their status, in this case conveniently converted to Antipodean time, where this author is based.<\/p><\/div>\n
Beyond SpaceX, the Texas Space Launch Schedule <\/span><\/a> is a useful tool<\/strong> for forward planning around upcoming launch windows. And finally, Space Notices <\/span><\/a> is worth a look too. It\u2019s privately-run but provides a useful \u2018big picture\u2019 view that shows full hazard areas across all FIRs involved, not just one.<\/strong><\/p>\n
Cover yourself<\/h4>\n
Beyond briefing, there are some things you can do to further lessen the impact of SpaceX launches on your flight.<\/p>\n
On a known launch day, plan to cross the corridor before the window opens.<\/strong> Don\u2019t be tempted to show up right after a scheduled launch because if it\u2019s delayed (and they often are) you\u2019ll be heading right into the action.<\/p>\n
For flights near the Gulf or northwest Caribbean, check the status of a launch right up to departure,<\/strong> not just when you\u2019re flight planning. Lest a mysterious and unexpected Notam suddenly appears that wasn\u2019t in your briefing pack.<\/p>\n
It doesn\u2019t end there either. It may be a good idea to have someone on the ground monitoring Space X\u2019s status page<\/strong> who can then relay that information to the crew in the air. Just because you were all clear on departure, doesn\u2019t mean you will be when you arrive.<\/p>\n
And finally, don\u2019t assume one FIR\u2019s Notams tell the whole story.<\/strong> If your route takes you anywhere near a Starbase launch corridor, check the Notams for the FIRs adjacent to your track too – not just the one you\u2019re flying through.<\/p>\n
Look out in a few weeks time<\/h4>\n
The next mission, Starship 14, is slated to launch in early September.<\/strong> When a date is announced, we\u2019ll be sure to let you know.<\/p>\n
A special thank you to the pilots involved who brainstormed their lessons-learned for the benefit of our group! We salute you!<\/p>\n
And one final tidbit. Remember when SpaceX launched a Tesla Roadster into space aboard a Falcon Heavy back in 2018? It’s still out there\u00a0– last tracked millions of miles from Earth in an orbit around the sun. Starman the mannequin is still in the driver’s seat.<\/p>\n
\"\"<\/p>\n
\"image_pdf\"<\/a><\/div>","protected":false},"excerpt":{"rendered":"
On July 24 one of our members\u2019 aircraft – a medevac jet – departed MGGT\/Guatemala…<\/p>\n","protected":false},"author":49,"featured_media":31143,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[584,2042,155],"class_list":{"0":"post-31138","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-briefings","8":"tag-airspace","9":"tag-launch","10":"tag-spacex"},"_links":{"self":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/31138","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/users\/49"}],"replies":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/comments?post=31138"}],"version-history":[{"count":46,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/31138\/revisions"}],"predecessor-version":[{"id":31218,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/31138\/revisions\/31218"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media\/31143"}],"wp:attachment":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media?parent=31138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/categories?post=31138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/tags?post=31138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}