Network Rumors and facts
#211
I'm well aware of that. That wasn't the case years ago where you needed 2 HFs for dispatch into the WATRS (now WATS). It was changed a few years back to allow only 1 HF (most aircraft flying those routes have SATCOM now - not just talking DAL here either).
We meet on regular schedule with the Oceanic Control Centers. All carriers that participate attend. We send an operations rep to these meetings. The info coming out of the last few meetings is that WATS, according to New York Oceanic, will require SATCOM (CPDLC) capability for dispatch on the "L" routes. Without it, you won't be able to dispatch a flight on any WATS route. That's where Oceanic is moving. Not sure when, or if there will be major push back from the air carriers.
It's the shear volume of traffic moving up and down the L routes that is driving this. The HF is antiquated and task centric. It's sufficient for a backup should SATCOM fail enroute. The issue they are having is when that one HF fails. Also, how do you maintain flight control when you can't reach your company? Yes, you might relay POS reports thru someone that has working HF/SATCOM, however if you have a maintenance issue, med emergency, or some other related issue, without your one HF working, you are sort of out of span of control at that time. You might only see one little piece as an operator out there in your limited use you personally have flown. However, NY Oceanic sees thousands of flights over months at a time and they have all the info on what does and does not work out there. Thus the push for them to demand a minimum of SATCOM capability for dispatch onto those routes. It's coming. Again, not sure of the timeline.
We meet on regular schedule with the Oceanic Control Centers. All carriers that participate attend. We send an operations rep to these meetings. The info coming out of the last few meetings is that WATS, according to New York Oceanic, will require SATCOM (CPDLC) capability for dispatch on the "L" routes. Without it, you won't be able to dispatch a flight on any WATS route. That's where Oceanic is moving. Not sure when, or if there will be major push back from the air carriers.
It's the shear volume of traffic moving up and down the L routes that is driving this. The HF is antiquated and task centric. It's sufficient for a backup should SATCOM fail enroute. The issue they are having is when that one HF fails. Also, how do you maintain flight control when you can't reach your company? Yes, you might relay POS reports thru someone that has working HF/SATCOM, however if you have a maintenance issue, med emergency, or some other related issue, without your one HF working, you are sort of out of span of control at that time. You might only see one little piece as an operator out there in your limited use you personally have flown. However, NY Oceanic sees thousands of flights over months at a time and they have all the info on what does and does not work out there. Thus the push for them to demand a minimum of SATCOM capability for dispatch onto those routes. It's coming. Again, not sure of the timeline.
Meanwhile our former ETOPS 737-900's were doing PNS and HSV turns out of ATL every day.....Brilliant use of resources!
Glad the guv-mint is requiring it because Delta apparently wasn't smart enough to figure it out on their own.
#212
Can’t find crew pickup
Joined: Jun 2021
Posts: 3,037
Likes: 189
I'm well aware of that. That wasn't the case years ago where you needed 2 HFs for dispatch into the WATRs (now WATs). It was changed a few years back to allow only 1 HF (most aircraft flying those routes have SATCOM now - not just talking DAL here either).
We meet on regular schedule with the Oceanic Control Centers. All carriers that participate attend. We send an operations rep to these meetings. The info coming out of the last few meetings is that WATs, according to New York Oceanic, will require SATCOM (CPDLC) capability for dispatch on the "L" routes. Without it, you won't be able to dispatch a flight on any WATS route. That's where Oceanic is moving. Not sure when, or if there will be major push back from the air carriers.
It's the shear volume of traffic moving up and down the L routes that is driving this. The HF is antiquated and task centric. It's sufficient for a backup should SATCOM fail enroute. The issue they are having is when that one HF radio you have with nothing else, fails. Also, how do you maintain flight control when you can't reach your company? Yes, you might relay POS reports thru someone that has working HF/SATCOM, however if you have a maintenance issue, med emergency, or some other related issue, without your one HF working, you are sort of out of span of control at that time. You might only see one little piece as an operator out there in your limited use you personally have flown. However, NY Oceanic sees thousands of flights over months at a time and they have all the info on what does and does not work out there. Thus the push for them to demand a minimum of SATCOM capability for dispatch onto those routes. It's coming. Again, not sure of the timeline.
We meet on regular schedule with the Oceanic Control Centers. All carriers that participate attend. We send an operations rep to these meetings. The info coming out of the last few meetings is that WATs, according to New York Oceanic, will require SATCOM (CPDLC) capability for dispatch on the "L" routes. Without it, you won't be able to dispatch a flight on any WATS route. That's where Oceanic is moving. Not sure when, or if there will be major push back from the air carriers.
It's the shear volume of traffic moving up and down the L routes that is driving this. The HF is antiquated and task centric. It's sufficient for a backup should SATCOM fail enroute. The issue they are having is when that one HF radio you have with nothing else, fails. Also, how do you maintain flight control when you can't reach your company? Yes, you might relay POS reports thru someone that has working HF/SATCOM, however if you have a maintenance issue, med emergency, or some other related issue, without your one HF working, you are sort of out of span of control at that time. You might only see one little piece as an operator out there in your limited use you personally have flown. However, NY Oceanic sees thousands of flights over months at a time and they have all the info on what does and does not work out there. Thus the push for them to demand a minimum of SATCOM capability for dispatch onto those routes. It's coming. Again, not sure of the timeline.
#213
Gets Weekends Off
Joined: Jan 2023
Posts: 3,390
Likes: 820
Believe it or not there's not many out there on the "L" routes without SATCOM. It's just the ones who don't have it are few, but stepping all over each other! That's one of the issue NY Oceanic brings up, thus why I state it's "task centric" for the operators.
#214
I can attest. Most of the time we had no SATCOM on the WATRS routes. But had one every time flying ATL/CHS. Someone somewhere in a cubicle didn't never seemed to plan that right.
#215
Gets Weekends Off
Joined: Jan 2023
Posts: 3,390
Likes: 820
Yet somehow the 75 fleet was able to figure out what jets had SATCOM and dispatch them appropriately. Yeah, I've heard about the 73 SATCOM birds not being used on the WATs routes, and I scratch my head on that one. Not sure what that fleet is up to there. It's not hard to do, again the 75 fleet had figured it out. I guess it will take the dot gov to regulate this and force their hand eventually. Or the NEOs solely take over that flying. IDK, not in the network room anymore.
#216
Gets Weekends Off
Joined: Jan 2023
Posts: 3,390
Likes: 820
Perhaps those ATL fellas needed to call in to pre-order their Miss Mary's low country boil for the overnight???
Anyway back to the thread...
#218
Gets Weekends Off
Joined: Jan 2023
Posts: 3,390
Likes: 820
Is that from a fleet bulletin/standards letter? When I was in strat planning I don't recall us making that an option, again we were looking and making plans for many jets (350, 78, NEO 321, MAX, the now A220, 330 NEO, etc). I could have forgot, but I don't recall that as an option. Happy to be wrong about though.
#219
#220
On Reserve
Joined: Jan 2025
Posts: 163
Likes: 64
The talk years ago was the 737 leaders begged FOPs to only put the SATCOM jets on WATRS. They were essentially told TechOps didn't want to/or couldn't guarantee it would work with their scheduling or something to that effect. In the end, it wasn't for a lack of effort, it was more because of TechOps (great people they may be).
Last edited by Bazinga; 02-17-2026 at 11:13 AM.
Thread
Thread Starter
Forum
Replies
Last Post




