QatarEnergy chief executive Saad Sherida Al-Kaabi said on Sunday, 20 September, that some of the company\u2019s expansion projects could be delayed because critical equipment is unable to reach Qatar through the disrupted Strait of Hormuz. Speaking at the Qatar Economic Forum powered by Bloomberg, the UNGA Special Edition 2026 in New York, in a session titled \u201cGeopolitics and Energy Security in Global Markets,\u201d Al-Kaabi, who is also Qatar\u2019s minister of state for energy affairs, separated current output from project logistics: Ras Laffan is producing only a \u201cvery minute\u201d volume of LNG, while inbound equipment for the North Field build-out remains blocked.<\/p>\n
He kept the near-term construction message constructive. \u201cNorth Field East is going very well. We expect the first train to come online in the first half of next year, and then possibly a few more trains from NFE to come next year. North Field South (NFS) is also going well,\u201d he said, according to The Peninsula<\/em>. The caveat followed immediately: some equipment will not be able to enter because of the Hormuz crisis, and if that continues it could delay some of these projects. Reuters reported the same warning on 20 September and, in a 21 September follow-up, that additional NFE trains will depend on the strait crisis even if the first train remains aimed at the first half of 2027.<\/p>\n QatarEnergy has not published a revised startup date. The company is signalling execution risk, not confirming that North Field East or North Field South will start late. For operators the distinction still matters: Hormuz is no longer only an outbound cargo problem. It is also an inbound project-cargo and commissioning problem for the world\u2019s largest LNG expansion.<\/p>\n Al-Kaabi was answering a live market question: how fast can Qatar restore LNG if the strait reopens? His reply, as carried by The Peninsula<\/em>, was that \u201cwith the subtraction of the 17 percent, we can get back to normal operations within a couple of weeks.\u201d The 17 percent is not a Hormuz shipping haircut. It is the share of Qatari LNG export capacity lost when missile strikes hit Ras Laffan Industrial City on 18\u201319 March 2026. QatarEnergy said in March that the attacks damaged Trains 4 and 6, together 12.8 million tonnes per annum, and that the damage could cost about $20 billion a year in lost revenue and take up to five years to repair. Train 4 is a QatarEnergy\u2013ExxonMobil joint venture (66\/34); Train 6 is 70\/30. Those trains stay out of the restart math. The rest of the system, he said, could be brought back in a couple of weeks if Hormuz opens \u2014 provided ships can actually load and sail.<\/p>\n That is not the picture today. Asked about Ras Laffan production, Al-Kaabi said it was \u201cvery difficult to put a number, because from an LNG perspective, it\u2019s very minute what we\u2019re producing.\u201d Domestic gas, jet fuel, gasoline, diesel and electricity were being covered, and some petrochemical units had land access to export, \u201cbut the majority of our production is not producing.\u201d Iran International and Reuters both repeated the \u201cvery minute\u201d LNG characterisation from the same New York session.<\/p>\n The North Field programme is the piece that now sits behind the equipment bottleneck. QatarEnergy\u2019s own project materials describe North Field East as four liquefaction trains of 8 MTPA each, adding 32 MTPA and lifting nameplate capacity from 77 MTPA to 110 MTPA. North Field South adds two further 8 MTPA trains, taking the total to 126 MTPA, with North Field West another 16 MTPA toward 142 MTPA by the end of 2030. Al-Kaabi said NFE is already in a commissioning-adjacent phase for the first train, with further NFE trains possible in 2027 and NFS trains the following year. Reuters\u2019 21 September write-up put the first NFE train in the first half of 2027 and said later trains will depend on whether Hormuz keeps blocking equipment.<\/p>\n Shipping context around that warning is thin, not closed. Reuters, citing Kpler, reported on Monday that 17 commodity vessels transited Hormuz over the weekend, down from 37 a week earlier, against a pre-war run-rate of about 125 large commercial ships a day. Among the hulls that did show, the LNG carrier Shandong Redwood exited on 19 September with a Ras Laffan cargo bound for Pakistan. Earlier in the week, three LNG carriers \u2014 Al Daayen, Al Samriya and Marigold LNG \u2014 reappeared outside the strait after days of reduced visibility, and Kpler had Al Rayyan in a dark STS off Oman. Those movements keep individual cargoes alive. They do not restore a reliable inbound lane for heavy modules, compressors, electrical packages and vendor specialists that a train-commissioning sequence needs on a calendar.<\/p>\n Al-Kaabi also used the same session to update non-Qatar LNG and petrochemical clocks that operators should not confuse with NFE. Golden Pass LNG in the United States has started shipments from the first train, with the second and third trains expected in full operation next year. The Golden Triangle ethane cracker with Chevron Phillips, in which QatarEnergy holds 49 percent, was entering commissioning and \u201cshould be starting up in the next few weeks.\u201d Those U.S. clocks are not Hormuz-constrained in the same way. The equipment warning is about getting kit into Qatar.<\/p>\n For LNG carrier owners and charterers, two clocks are now running. The cargo clock is the one already visible in AIS: minute Qatari loadings, occasional Pakistan or STS stems, long idle or holding patterns outside the Gulf, and a restart that Al-Kaabi says could be measured in weeks if the strait reopens \u2014 minus the 17 percent of capacity already destroyed at Ras Laffan. The project clock is slower and less visible. If specialised equipment stays offshore or in origin yards because it cannot enter, later NFE trains and NFS can slip even while the first NFE train is still described as first-half 2027. QatarEnergy has not said which packages are stuck. Operators should not invent a delay in months; they should treat 2027\u201328 delivery windows as having a Hormuz-logistics rider.<\/p>\n That rider reaches the fleet as well as the plant. QatarEnergy\u2019s expansion was planned as trains plus ships. New cargoes need new LNG carriers; new carriers delivered into a delayed cargo wave change utilisation, ballast and time-charter cover. A short equipment interruption may be absorbed in construction sequencing. A prolonged block on critical-path items \u2014 and Al-Kaabi framed the risk as continuing until equipment can enter \u2014 can move commissioning, first gas and the moment those ships have contracted molecules to lift.<\/p>\n For project-cargo and heavy-lift operators the implication is more immediate. A module that cannot enter Hormuz is not only a QatarEnergy problem. It is a voyage, war-risk, lay-up and storage problem at load ports, transshipment hubs and Gulf of Oman holding areas. Insurers already price Hormuz as a listed-area risk. Project policies that assumed a 2026\u201327 delivery window into Ras Laffan or Mesaieed now have to ask whether the kit waits, goes via an untested land bridge, or is stored until a facilitated transit exists. Crew, vendor specialists and commissioning staff face the same access constraint as the steel.<\/p>\n Buyers on long-term Qatari SPA volumes should also separate restart from replacement. A couple of weeks to resume undamaged trains is not the same as replacing Trains 4 and 6, which QatarEnergy has already said could take up to five years. Trading cover, destination flexibility and the company\u2019s stated push to become a much larger LNG trader are the commercial buffers Al-Kaabi pointed to; they do not put 12.8 MTPA of damaged Ras Laffan capacity back on the berth.<\/p>\n Regulas Shipping will keep monitoring QatarEnergy guidance, Ras Laffan loadings and Hormuz project-cargo movements, and will update operators if North Field dates are revised or if inbound equipment flows resume.<\/p>\n","protected":false},"excerpt":{"rendered":" QatarEnergy chief executive Saad Sherida Al-Kaabi said on Sunday, 20 September, that some of the company\u2019s expansion projects could be delayed because critical equipment is unable to reach Qatar through the disrupted Strait of Hormuz. Speaking at the Qatar Economic Forum powered by Bloomberg, the UNGA Special Edition 2026 in New York, in a session […]<\/p>\n","protected":false},"author":1,"featured_media":773,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wpai_generated_summary":"","wpai_meta_description":"","footnotes":""},"categories":[26,18,4],"tags":[],"class_list":["post-774","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-highlights","category-maritime-industry","category-maritime-security"],"_links":{"self":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/774","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/comments?post=774"}],"version-history":[{"count":1,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/774\/revisions"}],"predecessor-version":[{"id":775,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/774\/revisions\/775"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/773"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=774"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=774"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=774"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Incident context<\/h2>\n
Operational implications<\/h2>\n
What Operators Should Note<\/h2>\n
\n