Travel Waiver: Winter Storm "Avery" (15-Nov-18 - 17-Nov-18)
Nov 14, 2018, 11:39 pm
#1
FlyerTalk Evangelist
Original Poster
Join Date: Jun 2010
Location: TOA
Programs: HH Diamond, Marriott LTPP/Platinum Premier, Hyatt Lame-ist, UA !K
Posts: 20,061
Travel Waiver: Winter Storm "Avery" (15-Nov-18 - 17-Nov-18)
Just posted: https://www.united.com/CMS/en-US/travel/news/Pages/travelnotices.aspx#ExceptionPolicies
Good. luck to all over these next few days. Including myself.
David
Good. luck to all over these next few days. Including myself.
David
Nov 15, 2018, 12:08 am
#3
Moderator: United Airlines
Join Date: Jun 2007
Location: SFO
Programs: UA Plat 1.995MM, Hyatt Discoverist, Marriott Plat/LT Gold, Hilton Silver, IHG Plat
Posts: 66,832
an extensive list of airports in this waiver
- Wilkes-Barre/Scranton, PA (AVP)
- Hartford, CT (BDL)
- Bangor, ME (BGR)
- Boston, MA (BOS)
- Burlington, VT (BTV)
- Buffalo, NY (BUF)
- Baltimore, MD (BWI)
- Charlottesville, VA (CHO)
- Washington-National, DC (DCA)
- Elmira, NY (ELM)
- Erie, PA (ERI)
- New York/Newark, NJ (EWR)
- White Plains, NY (HPN)
- Washington, DC - Dulles (IAD)
- Ithaca, NY (ITH)
- New York-LaGuardia, NY (LGA)
- Lewisburg, WV (LWB)
- Harrisburg, PA (MDT)
- Manchester, NH (MHT)
- Plattsburgh, NY (PBG)
- Philadelphia, PA (PHL)
- Providence, RI (PVD)
- Portland, ME (PWM)
- Roanoke, VA (ROA)
- Rochester, NY (ROC)
- State College, PA (SCE)
- Shenandoah Valley, VA (SHD)
- Syracuse, NY (SYR)
- Quebec City, QB, CA (YQB)
- Montréal, QC, CA (YUL)
- Toronto, ON, CA (YYZ)
Nov 15, 2018, 1:37 am
#5
Join Date: Nov 2008
Location: Utrecht, the Netherlands
Programs: Marriott LTP, Hilton Gold, ITA Elite+, Cathay S, Singapore S, Hertz PC, Avis PC
Posts: 3,151
The fiance is flying OGG-SFO-EWR-AMS tomorrow/Friday in economy. Should I try to route her via IAH? Will United do this easily, or will the fare buckets need to be the same, in which case it might be better to wait until a flight gets cancelled?
Nov 15, 2018, 3:12 am
#6
Join Date: Dec 2014
Location: Haze gray and underway
Programs: UA 1K 2MM, HH Diamond, Marriott 'clink clink' Titanium
Posts: 1,784
or a car 
Nov 15, 2018, 4:35 am
#8
Join Date: Jan 2016
Posts: 622
should be really easy to get the reroute as long as origin and destination are the same. SFO and EWR are both under waiver, so yes I would reroute.
Nov 15, 2018, 4:48 am
#9
Join Date: Dec 2004
Location: BOS<>NYC<>BKK
Programs: UA 4.3MM LT-GS; AA1MM; Amtrak SE; MAR LT TITAN; PC Plat; HIL DIA; HYA GLOB
Posts: 4,391
So this is a bit OT, but since UA continues the practice -- and should NOT -- I'll mention why here.
The National Weather Service has an official to name tropical storms (i.e. hurricanes), in support of the UN's (World Meteorological Organization) global system of naming tropical cyclones. This is an international standard, supported by governments worldwide.
The National Weather Service has no mandate, nor authority, to name any other kind of storm, and does not do so nor condone the practice. There is a major weather outlet that has chosen to do so for many years, and others "copy" the practice, as UA has done so in the case of the waiver notice sent last night. The reason that this practice should not be done, is that public confusion would occur if different private sources used different names. For example, what if The Weather Channel called this storm "Avery," AccuWeather called it "Arthur," and Wxguy's WxService called it "Arturo" -- and each of us had different forecasts? Remember, only the NWS can issue official watches and warnings; in order to ensure there is no public confusion, other outlets can (and should) transmit official government advisories with attribution.
Bottom line: UA is fully with its right (and I support it) to issue statements and waivers that reference the event, i.e. "a major winter storm will affect the mid-Atlantic and Northeast today," but UA should not perpetuate the use of proper names for storms.
The National Weather Service has an official to name tropical storms (i.e. hurricanes), in support of the UN's (World Meteorological Organization) global system of naming tropical cyclones. This is an international standard, supported by governments worldwide.
The National Weather Service has no mandate, nor authority, to name any other kind of storm, and does not do so nor condone the practice. There is a major weather outlet that has chosen to do so for many years, and others "copy" the practice, as UA has done so in the case of the waiver notice sent last night. The reason that this practice should not be done, is that public confusion would occur if different private sources used different names. For example, what if The Weather Channel called this storm "Avery," AccuWeather called it "Arthur," and Wxguy's WxService called it "Arturo" -- and each of us had different forecasts? Remember, only the NWS can issue official watches and warnings; in order to ensure there is no public confusion, other outlets can (and should) transmit official government advisories with attribution.
Bottom line: UA is fully with its right (and I support it) to issue statements and waivers that reference the event, i.e. "a major winter storm will affect the mid-Atlantic and Northeast today," but UA should not perpetuate the use of proper names for storms.
Nov 15, 2018, 9:21 am
#11
Join Date: Sep 2014
Posts: 2,531
You could also wait to see how the storm develops. But you risk all the available seats IAH-AMS getting claimed by other people.
You could also do OGG-ORD-AMS.
Nov 15, 2018, 9:35 am
#12
Join Date: Mar 2012
Programs: Mileage Plus 1K; Marriott Platinum; Hilton Gold
Posts: 6,355
So this is a bit OT, but since UA continues the practice -- and should NOT -- I'll mention why here.
The National Weather Service has an official to name tropical storms (i.e. hurricanes), in support of the UN's (World Meteorological Organization) global system of naming tropical cyclones. This is an international standard, supported by governments worldwide.
The National Weather Service has no mandate, nor authority, to name any other kind of storm, and does not do so nor condone the practice. There is a major weather outlet that has chosen to do so for many years, and others "copy" the practice, as UA has done so in the case of the waiver notice sent last night. The reason that this practice should not be done, is that public confusion would occur if different private sources used different names. For example, what if The Weather Channel called this storm "Avery," AccuWeather called it "Arthur," and Wxguy's WxService called it "Arturo" -- and each of us had different forecasts? Remember, only the NWS can issue official watches and warnings; in order to ensure there is no public confusion, other outlets can (and should) transmit official government advisories with attribution.
Bottom line: UA is fully with its right (and I support it) to issue statements and waivers that reference the event, i.e. "a major winter storm will affect the mid-Atlantic and Northeast today," but UA should not perpetuate the use of proper names for storms.
The National Weather Service has an official to name tropical storms (i.e. hurricanes), in support of the UN's (World Meteorological Organization) global system of naming tropical cyclones. This is an international standard, supported by governments worldwide.
The National Weather Service has no mandate, nor authority, to name any other kind of storm, and does not do so nor condone the practice. There is a major weather outlet that has chosen to do so for many years, and others "copy" the practice, as UA has done so in the case of the waiver notice sent last night. The reason that this practice should not be done, is that public confusion would occur if different private sources used different names. For example, what if The Weather Channel called this storm "Avery," AccuWeather called it "Arthur," and Wxguy's WxService called it "Arturo" -- and each of us had different forecasts? Remember, only the NWS can issue official watches and warnings; in order to ensure there is no public confusion, other outlets can (and should) transmit official government advisories with attribution.
Bottom line: UA is fully with its right (and I support it) to issue statements and waivers that reference the event, i.e. "a major winter storm will affect the mid-Atlantic and Northeast today," but UA should not perpetuate the use of proper names for storms.
That seemed a mean spirited name for all those who would be disrupted. No risk of such misunderstanding if it would have been identified as Typhoon 18-23, or whatever number of typhoons have blown up across the Pacific this year.
Nov 15, 2018, 10:55 am
#14
Join Date: Nov 2008
Location: Utrecht, the Netherlands
Programs: Marriott LTP, Hilton Gold, ITA Elite+, Cathay S, Singapore S, Hertz PC, Avis PC
Posts: 3,151
You don't need the same fare bucket, there just needs to be one seat in the appropriate cabin (economy). If you think a re-route is wise, do it now. Don't wait for it to cancel.
You could also wait to see how the storm develops. But you risk all the available seats IAH-AMS getting claimed by other people.
You could also do OGG-ORD-AMS.
You could also wait to see how the storm develops. But you risk all the available seats IAH-AMS getting claimed by other people.
You could also do OGG-ORD-AMS.
This is one long travel day for her though! 10:20 PM overnight to SFO then SFO-EWR then another overnight to AMS. Done it once myself, never again! haha
Nov 15, 2018, 10:58 am
#15
Join Date: Nov 2007
Location: Colorado
Programs: UA Gold (.85 MM), HH Diamond, SPG Platinum (LT Gold), Hertz PC, National EE
Posts: 5,652
Don't think there is a OGG-ORD flight today, at least I cannot find it with Google Flights. As it looks now, she would only arrive at EWR on Friday around 3PM, weather.com doesn't predict any snow tomorrow, so I think I'm gonna wait and see how the storm develops.
This is one long travel day for her though! 10:20 PM overnight to SFO then SFO-EWR then another overnight to AMS. Done it once myself, never again! haha
This is one long travel day for her though! 10:20 PM overnight to SFO then SFO-EWR then another overnight to AMS. Done it once myself, never again! haha
