1

WG/HWSOR 2017 ACTION ITEMS

(Planning Documents rev- 14Mar2017 MASTER r20170403)

Yellow highlights indicate changes to the NHOP 2016.

Gray highlighting indicates Action Item executed by WG staff.

NEW ACTION ITEMS FOR 71th IHC/TCRF

1 Title

Submitter

Submitted

Discussion

Recommendation

Replace Appendix L with new FAA MSN Coord Sheet

J.Britt Woods, Lt Col 53rd WRS, CDR Catherine Martin NOAA AOC, Rich Henning NOAA AOC

03 Feb 2017

During an annual meeting between the 53rd and NOAA AOC we were able to agree upon an improved and

standardized WRA setup sheet.

We would like to have it replace Appendix L in the NHOP.

2

Action

Recommended

Status:14Mar17

Status:20Mar17

WG staff replaces Coordination Sheet in NHOP Appendix L (wholesale replacement) upon ratification by

Working Group.

RATIFIED.

Appendix L submitted for publication to EM.

2 Title

Submitter

Submitted

Discussion

Proposed Retiring of NOAA/NESDIS/SAB Dvorak Classification Worldwide

Jessica Schauer, NWS Tropical Program Leader, and Robert Falvey, JTWC Director

3 February 2017

UPDATE FEBRUARY 1. 2017: NESDIS is now considering retiring all Dvorak classification world-wide. No

timeline was available for this decision at the time action items were sent to the Working group.

JANUARY 6. 2017: After more than 40 years of providing Dvorak analyses globally, NESDIS has decided to retire

SAB’s Dvorak estimates in the Eastern and Southern Hemisphere, including portions of the NWS area of responsibility

3

Recommendation

Action

Recommended

Status: 03Mar17

Status:06Mar17:

Status 14Mar17:

Status:04Apr

in the western Pacific. A 30-day comment period on this proposed retirement closed on 11/18/16. Per the comment

opportunity, NWS contacted NESDIS to request reconsideration of this termination.

The NWS Pacific Region has identified clear needs for this information as nearly 40 percent of the tropical cyclone

position and intensity estimates available to NWS offices in the western North Pacific and Southwest Pacific Oceans

come from SAB. Satellite surveillance of tropical cyclones within the expansive areas of forecast responsibility for

NWS offices in the western Pacific is critical since airplane reconnaissance and weather radar are extremely

limited. The Dvorak estimates performed by SAB are used directly by the Joint Typhoon Warning Center (JTWC) and

the Regional Specialized Meteorological Centers (RSMC) in Nadi, Fiji and Tokyo, Japan to provide the NWS offices

in Pacific Region valuable tropical cyclone analyses that directly benefit their tropical cyclone forecast products. In

addition, position estimates from SAB are used to determine the initial location of a tropical cyclone center in the NWS

Global Forecast System (GFS) model analysis, the primary numerical forecast guidance used in this region. Finally,

the Federal Emergency Management Agency (FEMA) Region IX has requested that the NWS improve its tropical

cyclone services in the western Pacific. The proposal to discontinue Dvorak estimates from SAB would clearly limit

the ability of the NWS to meet this request.

The NOAA Hurricane Conference concurred with the NWS request for NESDIS to reconsider the proposal to retire

Dvorak classifications within the NWS area of responsibility. Concurrence is now sought from the Working Group

to be passed along to NOAA/NESDIS.

Review by the WG-HWSOR meeting 15 March 2017. Submitters seek endorsement from the WG-HWSOR. No

other action appears necessary.

Suggested submitter coordinates with JTWC. JTWC is in agreement per email from Falvey. /DM

NESDIS will be present at the WG meeting and provide the following information (M. Turk):

1. NESDIS / OSPO will continue to provide worldwide ADT products.

2. NESDIS / OSPO continues to evaluate the SAB Dvorak product and has engaged senior NWS leadership on

this dialog. This process is still in work, and there are no planned changes for this hurricane season.

WG staff recommends to the submitters rewording the recommendation to the following given the lack of clarity

concerning possible changes to the Dvorak areas covered by NESDIS: The NOAA Hurricane Conference concurred

with the NWS request for NESDIS to reconsider the proposal to retire Dvorak classifications. Concurrence is now

sought from the Working Group to be passed along to NOAA/NESDIS.

Requested “endorsement” action did not carry. Ellen Ramirez representing NESDIS has contact POCs for NWS and

NESDIS in this matter for members of NWS and NESDIS to provide further feedback.

Will publish a Record of Action after the meeting. /OFCM/JS

Proposal for WG – WG acknowledges the positions of DOC and DOD operational centers as well as the programmatic

resources concerns of NESDIS, and calls for agencies to reach a solution that does not result in a significant

degradation of services. This information would be sent to the leadership involved in discussion.

ACTION – ELLEN RAMIREZ, BOB FALVEY AND MIKE BRENNEN WILL PREPARE WG RESPONSE IN

COORDINATION WITH NESDIS, DOD and NWS REPS AT MEETING FOR FORWARDING ON BEHALF

OF GROUP TO WG STAFF.

Draft text received, quoted below:

Draft Statement for WG AI2

Updated March 29 2017

The WG acknowledges the operational need and concerns of NHC, CPHC, and JTWC, and the fiscal and

programmatic concerns of NESDIS in regards to the proposed termination of SAB subjective Dvorak analyses. The

WG encourages senior leadership in NHC, CPHC, and JTWC to elevate concerns within the respective chains of

command. The WG recommends that NWS and NESDIS management find a solution that avoids any significant

operational degradation.

4

Background Material

National Hurricane Center Response to Proposed Elimination of Operational Tropical Cyclone Classifications

by the NESDIS Satellite Analysis Branch 16 February 2017

The National Hurricane Center (NHC) believes that a discontinuation of the NESDIS Satellite Analysis Branch (SAB)

tropical cyclone Dvorak classification program would have a negative effect on NHC’s tropical cyclone operations, for

the reasons given below. NHC believes that SAB should continue to provide this function in support of the Nation’s

hurricane program.

Satellite-based estimates of tropical cyclone position and intensity are crucial to NHC operations. In the

Atlantic basin, aircraft reconnaissance data are available to NHC forecasters for only about one-third of all

forecasts prepared, and for virtually none of the forecasts prepared for eastern North Pacific cyclones.

SAB has for more than three decades consistently provided high-quality location and intensity estimates to

the NHC for tropical cyclones and disturbances in both the Atlantic and the eastern North Pacific basins. The

SAB Dvorak products serve as an important second opinion to the Dvorak products generated by the

Tropical Analysis and Forecast Branch (TAFB) of the NHC, in much the same way that having multiple

numerical weather prediction models are useful to forecasters in the National Weather Service (e.g., the

“National Blend”). Loss of the SAB Dvorak products would increase the chance of mis-located tropical

cyclone centers or incorrectly analyzed tropical cyclone intensities, which would degrade the quality of the

NHC forecasts, just as reliance on a single weather prediction model would significantly increase the chance

of a poor forecast.

SAB Dvorak products currently provide continuity of operations (COOP) capability if the NHC facility were

to become unusable due to either a natural or man-made disaster. WPC forecasters (or NHC forecasters

deployed to WPC) in a COOP role would have no access to Atlantic basin Dvorak products during such an

event if SAB were to discontinue their Dvorak program.

Attempts continue to automate the Dvorak technique (ADT), but NHC does not consider the technique to be

a suitable replacement for SAB’s subjective classifications. ADT root-mean-square intensity errors overall

are comparable to but slightly larger than SAB intensity errors (11.79 kt vs 11.05 kt for a sample of 108 cases

during the past two Atlantic hurricane seasons). However, the ADT struggles with systems below hurricane

strength. In addition, the ADT does not run until a system has already become a tropical cyclone; thus, the

ADT cannot help a forecaster to decide when a disturbance has developed enough organized deep convection

to qualify it as a tropical cyclone. The current SAB products make an important contribution to that

decision-making process. Finally, in these situations there would be no ADT guidance on where the

system’s center is located, at a stage of development when location uncertainty is particularly large, making a

second opinion particularly valuable.

Intensity estimates from several low-earth orbit (LEO) microwave sounding units are available to

NHC. However, these are not suitable to replace manually created Dvorak products due to the latency of the

data. In addition, while the SAB products are coordinated with NHC’s forecast cycle, the LEO satellite

overpasses of tropical cyclones are not, and there are significant temporal gaps in the availability of these

estimates due to the overpasses missing the tropical cyclones.

The SAB has a significant international presence through its Dvorak products, which are available to tropical

cyclone warning centers world-wide. This includes the Central Pacific Hurricane Center, which provides

tropical cyclone data and forecasts for the Hawaiian Islands, and the U. S. Joint Typhoon Warning Center,

which provides tropical cyclone data and forecasts for U. S. military operation across much of the world.

Response to NHC Comments from NESDIS Management

29 March 2017

For approximately 40 years, NESDIS SAB has been providing Dvorak analyses worldwide on a 24x7x365

basis, which duplicates the WMO mandated efforts of NHC, CPHC, and other RSMCs. Today the NWS has

similar access to Geostationary and Polar satellite data, and so NESDIS management is evaluating if this

function still remains in our core mission. The role of NESDIS is to operate and manage the U.S.

environmental satellites whereas NWS is responsible for issuing official watches / warnings / forecasts.

NESDIS management has proposed the termination of manual Dvorak analyses of the Satellite Analysis

Branch, effective November 30, 2017. There is no timeline for a decision. Discussions include the following

NESDIS personnel: Mark Paese, NESDIS Deputy Assistant Administrator, Vanessa Griffin, NESDIS Office

of Satellite and Product Operations (OSPO) Director, Richard Marlow, NESDIS OSPO Deputy Director

5

Action

Recommended

The threat of severe NESDIS budget cuts further undermines the ability of NESDIS to staff weather watches

that are formally slated to be performed by NWS personnel.

All automated tropical products produced by NESDIS/OSPO will remain intact, including but not limited to

ADT, MTCSWA, and eTRaP.

SAB is struggling to maintain expertise. Fifty percent of analysts have less than 2 years’ experience. Three of

the 10 Dvorak analysts do not have a degree in meteorology.

NHC conducted a study comparing SAB Dvorak to ADT. The sample included 108 cases from the past 2

Atlantic seasons and it found SAB to be comparable to ADT (11.05 kts RMSE for SAB and 11.79kts RMSE

for ADT).

With regard to NHC concerns about storms too weak to be covered by ADT, note that on or around May 15 th,

2017, pending final approval by NWS, NHC will begin issuing watches, warnings, and graphical and textual

products on “potential TCs”, meaning disturbances that are not yet a TC. Those could be used to initialize the

ADT.

While NHC has indicated that they feel SAB is the COOP for this function, SAB was unaware of this and no

communications, procedures or agreement is in place for SAB to perform this role. Tropical analysts are also

responsible for the operation of the Washington VAAC, which takes priority over all tropical duties.

Review by WG-HWSOR and forward with WG endorsement/consensus.

3 Title

Submitter

Submitted

Discussion

Recommendation

Action

Recommended

Status: 03Mar17

Status: 06Mar17

Addition of Email to NHOP Telephone Listing (Appendix I)

Jessica Schauer, NWS Tropical Program Leader; CAPT Tim Gallagher, NOAA AOC, Tampa, FL

3 February 2017

Aircrews are currently using fax/phone technology to coordinate mission planning with air traffic

controllers. Providing emails for centralized distribution to air traffic controllers will help NOAA and Air Force

Hurricane Hunter flight crews to coordinate missions, to include the extended use of the Weather Reconnaissance Area

(WRA).

Endorsed by the 2016 NOAA Hurricane Conference and sent to the Working Group.

Air Traffic Control Agencies currently listed on the NHOP Telephone Listing (Appendix I) should provide email

contact information for distribution lists for flight crews to scan/submit mission coordination documents for

research/reconnaissance flights.

Recommend ATC agencies listed in Appendix I provide email contact information prior to WG-HWSOR

meeting on 15 March 2017 for inclusion in the 2017 NHOP Appendix I by WG-HWSOR staff.

Request made to FAA reps (John Kehler and Roger Rapier) for guidance. /DM

Request redirected to Hank Tracy (FAA ZMA ARTCC, Military and Special Operations). Received LOA listing ATC

6

Status:14Mar17

email contacts.

Risk of publishing emails in NHOP. Will not publish in NHOP. FAA LOA will be added to the NHOP and will

include contact information. ACTION NOT ADOPTED AND STAKEHOLDERS WILL COORDINATE THIS

INFORMATION. ACTION ITEM CLOSED PER SUBMITTERS.

7

4 Title

Submitter

Submitted

Discussion

SHOUT Global Hawk TC Forecast Demonstration Project

Jessica Schauer, NWS Tropical Program Leader; Vijay Tallapragada, Avichal Mehra (NWS-NCEP-EMC) 3

February 2017; rev 31 March 2017

The goal of this proposed operational demonstration project is two-fold. First, we seek to enhance NRD-94

‘minisonde’ sampling deployment locations from the Global Hawk platform of the TC upper environment and

outflow layer in regions of enhanced ensemble model uncertainty, thus improving targeting strategy over

deterministic model techniques used for TC surveillance flights during the past 10 years. Second, we seek to enhance

NWS-NCEP-EMC TC model predictions by reducing track and intensity forecast errors for both operational GFS

global model predictions and HWRF regional model using new NRD-94 dropsondes coupled with improved

targeting strategies and data formats. These goals are intended to serve as the foundation for future GH forecast

demo projects, as needed, as well as for developing a ‘collaborative’ or ‘backup’ strategy for existing manned

aircraft hurricane reconnaissance and surveillance missions.

From 2012-2014 the NASA Global Hawk High-Altitude, Long-Endurance (HALE) Unmanned Aerial

Vehicle (UAV) flew 21 research missions during the NASA Hurricane and Severe Storms Sentinel (HS3) program

over 9 named storms. From 2015-2016, the NOAA Sensing Hazards with Operational Unmanned Technology

(SHOUT) program flew a total 15 Rapid Response (RR) flights: 3 in EPAC El Niño/ Atmospheric River (AR) winter

storm systems and 12 in 2015-16 named Tropical Cyclones (TCs). The SHOUT 2016 TC Global Hawk flights

deployed 647 dropsondes within the TC inner core and surrounding environment, all of which were transmitted

using the standard TEMP DROP’ format over GTS to global modeling centers around the world. These data were

used in the NOAA HWRF and Navy COAMPS-TC regional models, as well as in ECMWF and UKMET global

models during 2016. They were not used in the NWS GFS global model.

Using a NASA- NOAA partnership for SHOUT operational implementation in 2016, significant cost savings was

demonstrated for operation of the Global Hawk during SHOUT Rapid Response missions compared with HS3

research missions (~$14K/hr vs ~$80K/hr, respectively). It is anticipated that these cost savings could be replicated

in future NASA-NOAA Global Hawk piggyback missions, such as the upcoming NASA HOPE-EPOCH program in

August, 2017. This program could provide a test bed for NRD-94 minisonde deployment strategies as well as proof

of concept for reduction of track and intensity errors shown in the developmental test cases.

Preliminary data denial studies have shown 5-10% improvement in HWRF TC intensity and track prediction from

use of Global Hawk data during HS3 and SHOUT. Preliminary retrospective model runs using GH data denial

strategies with and without Global Hawk dropsonde data have shown nearly a 20% reduction in both track and

intensity forecast errors when using the GH dropsondes. Furthermore, retrospective runs comparing WPAC and

EPAC typhoon and hurricane runs occurring on days with and without Atlantic GH dropsondes data, showed 10-

15% improvement in the track and intensity forecast errors in these other basins as well. This suggests that not only

is there a positive downstream impact from GH drosponde data, but rather a global impact. If such a result can be

verified with additional observations, the impact of GH dropsonde data might be seen as a seminal improvement to

the GFS global model predictions across the globe.

An initial Operational SHOUT Global Hawk Demonstration Project is proposed, in which improvements in TC

intensity forecasts would be sought by operational targeting of ensemble global and regional model-high uncertainty

regions with enhanced GH NRD-94 ‘minisonde’ deployments as a piggyback enhancement to the NASA Goddard

project entitled East Pacific Origin and Characteristics of Hurricanes (EPOCH) mission science training program

planned during August, 2017 and operating from Armstrong Flight Research Center. Flights were planned to be

conducted primarily over Eastern Pacific hurricanes, but has been expanded to include Gulf of Mexico and Western

North Atlantic storms.

Real-time transmission of GH remotely-sensed observations such as EXRAD precipitation mapping radar and

HAMSR temperature and humidity profiles will be added as time and funding permit. Improved Operational, real-

time processing of NRD-94 minisondes would transmit observations to NOAA models via GTS. NOAA-SHOUT

would seek additional resources for continuation of demonstration flights in follow-on years. NOAA-NCEP will

provide operational model runs with improved data formats and DA schemes and will evaluate this this proposed

Demo Project on a yearly basis. proposed Demo Project on a yearly basis.

Operational, real-time processing of NRD-94 minisondes would transmit observations to NOAA models via GTS. NOAA-SHOUT

would seek additional resources for continuation of demonstration flights in follow-on years. NOAA-NCEP will provide operational

8

Recommendation

Action

Recommended

Status: 23Feb17

Status:03Mar17

Status:06Mar17

Status:14Mar17:

Status:31Mar17

NWS-NCEP-EMC requests support from WG-HWSOR for recommendation that the new NRD-94

‘minisonde’ real-time data be included in NCEP GFS data assimilation procedures, including actual

or estimated position information, during future piggyback Operational Demonstration Rapid

Response hurricane or high-impact weather event missions utilizing NASA Global Hawk UAS or from

NRD-94 deployments during operational missions with NOAA G-IV surveillance aircraft.

WG-HWSOR endorses proposed recommendation in keeping with similar endorsement from the

National Hurricane Center.

Requested clarification from submitters regarding second paragraph (who is called to conduct

operational SHOUT demo).

Submitters are updating this AI and will resend by Mon 06 Mar 2017. /DM Update received from

submitters and incorporated above. /DM

WG Staff recommends the “endorsement” language entered above in the “Action Recommended”.

Submitters agree with language in Action Recommended.

Seeking endorsement to continue these experiments and assimilate data in real-time at NCEP. This

is a data opportunity. EMC wants an endorsement for a demonstration project there centered on

data assimilation experiment internally. The standing text above (yellow) is adequate. /VT

UAS Program Office will require piggy back resources from NASA.

Received draft text.

5

Title

Submitter

Submitted

Discussion

Recommendation

Adding Reference of Abbreviated Communications Headings for Aerial Reconnaissance Messages

Steve Feuer, CARCAH and Maj. Jonathan Brady, USAFR/53 WRS

9 February 2017

The NHOP presently does not contain consolidated documentation of the abbreviated communications headings used

for all the different types of aerial reconnaissance observation messages generated and transmitted during missions.

Reference material depicting these headings is desired by the reconnaissance flying units and could be beneficial to a

larger audience.

Describe the communications headings of aerial reconnaissance messages in a new paragraph within Chapter 5 of the

NHOP that is similar to the content in para. 3.6 for NWS-issued products. Insert the material below as a new

paragraph 5.7.6 and increment the numbering of current para. 5.7.6 and subsequent paragraphs under section 5.7 by

one (i.e., 5.7.6. to 5.7.7., 5.7.7 to 5.7.8, etc.). Include the table and figure as well and increment the index numbers for

subsequent tables and figures in the chapter.

5.7.6. Aerial Reconnaissance Abbreviated Communications Headings.

Each type of aerial weather-reconnaissance message is assigned designated abbreviated communications headings that

are dependent on the geographical region. Table 5-3 provides the WMO and AWIPS abbreviated headers for each data

product. The WMO header consists of three groups. The first has four letters followed by a two-digit product index

number. The initial two letters of that group indicate the data type: UR for aerial reconnaissance horizontal

observations and UZ for aerial reconnaissance vertical observations. The next two letters depict the basin of the

observation: NT for Atlantic, PN for East and Central Pacific, and PA for West Pacific (see Figure 5-8). The second

element of the header has the ground location ICAO at which the message is received from the aircraft and

subsequently disseminated through channels described in paragraph 5.9.1. The remaining element is a date-time group

with the time listed in UTC. The AWIPS product ID contains five letters followed by a product index number. The

first three letters indicate the message type: REP for standard observations (RECCO, vortex, and dropsonde) and AHO

for high-density observations. The other two letters depict the basin location using the same geographical conventions

9

as the WMO header.

Insert a new Table 5-3 (below), renumber current Table 5-3 as 5-4, and current Table 5-4 as new Table 5-5.

Table 5-3. Summary of Aerial Reconnaissance Data Products and their Associated Headers

PRODUCT

WMO HEADER

AWIPS ID

RECCO (non-tasked mission)

Atlantic URNT10 ICAO ddhhmm REPNT0

East and Central Pacific URPN10 ICAO ddhhmm REPPN0

West Pacific URPA10 ICAO ddhhmm REPPA0

RECCO (tasked invest, tropical cyclone, or subtropical cyclone mission)

Atlantic URNT11 ICAO ddhhmm REPNT1

East and Central Pacific URPN11 ICAO ddhhmm REPPN1

West Pacific URPA11 ICAO ddhhmm REPPA1

Vortex Data Message

Atlantic URNT12 ICAO ddhhmm REPNT2

East and Central Pacific URPN12 ICAO ddhhmm REPPN2

West Pacific URPA12 ICAO ddhhmm REPPA2

TEMP DROP Code (dropsonde observation)

Atlantic UZNT13 ICAO ddhhmm REPNT3

East and Central Pacific UZPN13 ICAO ddhhmm REPPN3

West Pacific UZPA13 ICAO ddhhmm REPPA3

High-Density Observation

Atlantic URNT15 ICAO ddhhmm AHONT1

East and Central Pacific URPN15 ICAO ddhhmm AHOPN1

West Pacific URPA15 ICAO ddhhmm AHOPA1

NOTE: ICAO is KNHC (National Hurricane Center--primary) or KBIX (Keesler Air Force Base--backup) for data

messages originating from USAFR/53 WRS aircraft and KWBC (National Weather Service HQ) for data messages

originating from NOAA or other agency aircraft.

Figure 5-8. Geographical Basins in Aerial Reconnaissance Abbreviated Communications Headings

10

Action

Recommended

Status:14Mar17

Status:29Mar17

Add new Table 5-3 to Chapter 5, renumber following tables including old Table 5-3 now 5-4. Add new Figure

5-8, old 5-8 et seq. renumber 5-9, and so on.

Discuss at WG-HWSOR, if adopted then edit accordingly Chapter 5.

Accepted.

Sent updated Ch5 Word file to submitter (SF) for edits.

Update expected 02 Apr

Edits received Ch5.

6 Title

Submitter

Submitted

Discussion

Recommendation

Action

Recommended

Status:14Mar17

Status:21Mar17

Status:6Apr17

Revisions to HDOB Message Section in NHOP Appendix G

Steve Feuer, CARCAH

9 February 2017

Since the explanation of communications headers for HDOB messages is now incorporated into new para. 5.7.6 per

previous action item (#5 above), there no longer is a need for Table G-3. Also, some minor content adjustments need

to be made.

1) Change formatting at top of current p. G-6 to: "G.2.2. HDOB. The HDOB message is used to transmit..."

2) Eliminate current Table G-3. Change the beginning of the last sentence of the first paragraph on current p. G-6 to

the following:

"Each message consists of a communications header line described in Chapter 5, paragraph 5.7.6 (Table G-3), a

mission/ob..."

3) Change table references of current Table G-4 to Table G-5 and current Table G-5 to Table G-6.

4) In the fourth paragraph change "is given below" to "shown in Figure G-4" (change current Figure G-2 to Figure G-

4).

5) In Table G-4, change "paragraph 5.7.6" to "paragraph 5.7.7" for the description of item III...III.

Review at WG-HWSOR meeting. If approved, WG staff amends Appendix G, as recommended.

ADOPTED

Sent updated App G to submitter for editing as agreed by submitter.

Received updated Appendix G/posted to website.

7 Title

Submitter

Submitted

Discussion

Improved Organization and New Introduction for NHOP Appendix G

Steve Feuer, CARCAH

9 February 2017

Appendix G of the NHOP, which has documentation about RECCO, HDOB, and TEMP DROP codes, tables, and

regulations, has become a primary reference for these aerial reconnaissance data messages by NHOP participating

agencies and is linked to by several websites, including NHC's. It could be better organized with an overview

statement and paragraph headings to clearly demarcate the different sections dedicated to describing each type of aerial

reconnaissance data message.

11

Recommendation

Action

Recommended

Status:14Mar17

Status:21Mar17

Status:06Apr17

1) Add the following brief introductory paragraph:

G.1. General. This appendix contains the formats and detailed explanations of encoded data messages transmitted by

weather reconnaissance aircraft. The products include reconnaissance coded observations (RECCOs), high-

density/high-accuracy observations (HDOBs), and dropsonde observations (TEMP DROP).

2) Insert paragraph headers to mark the beginning of each section:

G.2. Aerial Reconnaissance Messages.

G.2.1. RECCO.

G.2.2. HDOB.

G.2.3. TEMP DROP.

Review at WG-HWSOR meeting. If approved, WG staff edits Appendix G, as recommended.

ACCEPTED.

Sent updated App G for editing BY SUBMITTER. Expect 02 Apr.

Received updated Appendix G/posted.

8

Title

Submitter

Submitted

Discussion

Recommendation

Improving RECCO Code Reference in NHOP Appendix G

Maj. Jonathan Brady, USAFR/53 WRS, and Steve Feuer, CARCAH

9 February 2017

The NHOP presently does not describe or fully define the RECCO code in Appendix G. It also does not contain

example RECCO messages in Appendix G, nor does it fully explain the decoding of these messages. Currently, the

only information available includes two legacy tables, a regulations page, and a RECCO encoding form, which are not

particularly user friendly. Personnel from both the 53 WRS and NOAA/AOC agree that additional documentation

would be helpful.

1) Add a RECCO Code description, a figure displaying two example RECCO messages (one from the USAF 53WRS

aircraft and one from NOAA aircraft), and two tables showing how to decode these messages. The new content is

provided below and would be placed prior to current Figure G-1 (change to Figure G-2), Table G-1 (change to Table

G-3), and Table G-2 (change to Table G-4) in Appendix G.

2) Propose to modify or revamp the RECCO legacy reference materials in Appendix G for future NHOP editions.

Insert new material starting with the following for RECCO section:

G.2.1. RECCO. The RECCO message is routinely used to convey horizontal weather observations taken manually by

meteorologists aboard USAF and NOAA weather reconnaissance aircraft. At the time of the observation the aircraft

observing platform is considered to be located on the axis of a right vertical cylinder with a radius of 30 nautical miles

bounded by the earth's surface and the top atmosphere. Flight level winds, temperature, dew point, and geopotential

height values are sensed or computed and reported as occurring at the center of the observation circle. Radar echoes,

significant weather changes, distant weather, icing, and cloud coverage, types, and amounts are phenomena that may

also be observed and reported. Code groups identifying these phenomena may be reported as necessary to adequately

describe the meteorological conditions observed. All geopotential computations are made relative to the 1976 US

Standard Atmosphere (adjustable altimeters set to 29.92 inches Hg). Since all height reports are in units of

geopotential by convention of the World Meteorological Organization, pressure surface height reports from

reconnaissance aircraft are in geopotential units.

12

Sample USAFR/53 WRS and NOAA RECCO messages are shown in Figure G-1. A breakdown of these messages is

provided in Tables G-1 and G-2. Figure G-2 shows the standard RECCO recording form worksheet with each element

described in Table G-3 and regulations explained in Table G-4.

URNT11 KNHC 041322

97779 13204 10295 56518 30500 22068 10089 /3051

42045

RMK AF305 1511A JOAQUIN OB 13

SWS = 41KTS

URNT11 KWBC 202029

97779 20284 50267 72800 04500 14009 24218 /0004 41311 93273

RMK NOAA3 01GGA INVEST OB 10

Figure G-1. Examples of Tropical Cyclone RECCO Messages from USAF and NOAA Aircraft

Table G-1. Decoded USAF Aircraft RECCO Message

URNT11 KNHC 041322

97779 13204 10295 56518 30500 22068 10089 /3051

42045

RMK AF305 1511A JOAQUIN OB 13

SWS = 41KTS

URNT11: WMO abbreviated communications header for a RECCO taken during a tasked

invest, tropical cyclone, or subtropical cyclone mission in the Atlantic basin (see

Chapter 5, paragraph 5.7.6 for details).

KNHC: ICAO of National Hurricane Center where RECCO message is received and

disseminated (see Chapter 5, paragraph 5.7.6 for details).

041322: RECCO transmission date and time is 4th day of the month at 1322 UTC.

97779: The 9’s in the first and last digits are standard delimiters of the first RECCO

observation section. The middle three digits, 777, indicate that the observation is

taken aboard an aircraft with radar capabilities (see “Table 1” section of Table G-3).

13204: The first four digits are the time observation is taken of 1320 UTC. The last digit, 4,

indicates the aircraft has dew point measuring capability and is below 10 km (see

“Table 2” section of Table G-3).

10295: The first digit, 1, indicates the observation is taken Sunday. The second digit, 0,

indicates the observation is taken in the northern hemisphere between 0° and 90° W

longitude (see “Table 3” section of Table G-3 and Figure G-3 for graphical

depiction). The last three digits show the observation is taken at 29.5° N latitude.

56518: The first three digits show the observation is taken at 56.5° W latitude (see Note 4 in

Table G-4). The fourth digit, 1, indicates light aircraft turbulence (see “Table 4”

section in Table G-3). The last digit, 8, indicates aircraft flight conditions of in and

out of clouds (see “Table 5” section of Table G-3 and Note 5 of Table G-4).

13

30500: The first three digits show the aircraft pressure altitude is 3050 m. The fourth digit,

0, indicates that the wind observation is a spot measurement (see “Table 6” section

of Table G-3). The last digit, 0, shows that the wind is obtained by Doppler radar or

inertial systems (see “Table 7” section of Table G-3).

22068: Observed Flight-level wind is approximately from 220° (between 215° and 224°) at

68 kt. Note: light and variable winds < 10 kt are encoded as 99005.

10089: The first two digits indicate the observed flight-level temperature is 10°C. The next

two digits indicate the flight-level dew point temperature is 8°C (see Note 6 of Table

G-4 for encoding negative temperature values). The last digit, 9, indicates that there

are thunderstorms within 30 nm of the aircraft (see “Table 8” section of Table G-3

and Note 7 of Table G-4).

/3051: The “/3” indicates an observed geopotential height measurement at 700 mb. The last

three digits show the height of 3051 m (see “Table 9” section of Table G-3 and Note

8 of Table G-4).

42045: The first digit, 4, indicates a manually observed surface wind from a flight level of

700 mb or below. The remaining four digits show that the surface wind is from

approximately 200° (between 195° and 204°) at 45 kt (see Note 10 in Table G-4 for

wind speeds above 130 kt). Note: light and variable winds < 10 kt are encoded as

99005.

RMK: Beginning of RECCO plain-language remarks section (see Note 3 of Table G-4).

AF305: Aircraft in mission ID is U.S. Air Force C-130J with tail number 5305 (see Chapter

5, Table 5-4 for details).

1511A: Index group in mission ID indicates the 15th mission of the 11th classified tropical or

subtropical system of the year in the Atlantic basin (see Chapter 5, Table 5-4 for

details).

JOAQUIN: Official name of system in mission ID is “Joaquin” (see Chapter 5, Table 5-4 for

details).

OB 13: Observation number 13 is assigned to this RECCO (see Chapter 5, paragraph 5.7.8

for details).

SWS=41KTS: Observed surface wind speed measured by SFMR is 41 kt.

Table G-2. Decoded NOAA Aircraft RECCO Message

URNT11 KWBC 202029

97779 20284 50267 72800 04500 14009 24218 /0004 41311 93273

RMK NOAA3 01GGA INVEST OB 10

All items are decoded in a similar manner to the USAF Aircraft RECCO message depicted in

Table G-1, except for the following:

/0004: The “/0” indicates an extrapolated sea-level pressure measurement . The last three

digits show the sea-level pressure of 1004 mb (see “Table 9” section of Table G-3

and Note 8 of Table G-4).

14

Action

Recommended:

Status:14Mar17

Status:21Mar17

Status:6Apr17

93273: The first digit, 9, indicates a sea-surface temperature measurement. The second digit,

3, indicates that the inflight visibility is greater than 3 miles (see "Table 23" section

of Table G-3). The last three digits show the observed sea-surface temperature is

27.3°C.

NOAA3: Aircraft in mission ID is NOAA WP-3D with tail number N43RF (see Chapter 5,

Table 5-4 for details).

01GGA: Index group in mission ID indicates the first mission of the 7th unclassified suspect

system of the year in the Atlantic basin (see Chapter 5, Table 5-4 for details).

INVEST: Indicates invest mission in the storm ID (see Chapter 5, Table 5-4 for details).

NOTE: The observed surface wind group, indicated by the first digit of 4, is placed on the same line as

the other numeric encoded groups in a NOAA aircraft RECCO message rather than on a separate line .

Figure G-3. Geographical Depiction of Octants Encoded in RECCO Messages

Review at WG-HWSOR meeting. If approved, WG staff will edit NHOP Appendix G as recommended.

ADOPTED. Legacy tables will still be in 2017 NHOP. Future revision may update this further and/or online at

NHC pending follow up.

Sent updated App G TO submitter for editing.

Received updated Appendix G/posted.

9 Title

Submitter

Submitted

Discussion

Improving TEMP DROP Code Reference in NHOP Appendix G

Maj Jonathan Brady, USAFR/53 WRS, and Steve Feuer, CARCAH

9 February 2017

The NHOP currently does not give an overview and summary explanation of the TEMP DROP message in Appendix

G. Also, some enhancements to the legacy content describing the code would be helpful.

15

Recommendation

1) Add the TEMP DROP code description below at beginning of section on current p. G-10:

G.2.3. TEMP DROP. The TEMP DROP code message provides a representation of quality-controlled vertical

measurements of pressure, temperature, moisture, and winds acquired from dropsondes released from reconnaissance

aircraft. The message consists primarily of two main sections: Part A and B. In Part A, temperature, dew point

depression, and wind measurements are reported at the surface and at every mandatory pressure level the dropsonde

traverses as it descends from flight level. A hydrostatically-computed seal-level pressure obtained from sonde data is

reported with the surface data. Calculated geopotential heights based on upward or downward hydrostatic integration

of the sonde data are also reported with the mandatory pressure levels. In Part B, thermodynamic (temperature and

dew point depressions) and wind measurements are reported at significant pressure levels traversed by the dropsonde

from flight level to the surface. The significant levels are selected from a quality-control algorithm where local

extrema occur in the vertical profiles of the thermodynamic and wind data and at other set criteria. Additional

information is provided in remarks lines at the end of each section, including but not limited to aircraft mission ID,

observation number, and dropsonde release and splash times and locations. If the dropsonde is released by an aircraft

at a pressure altitude above 100 mb, the TEMP DROP message will contain additional Parts C and D, which are

analogous to Parts A and B, for mandatory and significant level measurements < 100 mb.

Sample USAFR/53 WRS and NOAA TEMP DROP messages are shown in Figure G-5. A detailed explanation of

each element within a TEMP DROP message is presented in Table G-7.

2) Change current Table G-6 to Table G-7 and current Figure G-3 to Figure G-5.

3) In Part A section of current Table G-6 under the "MARSDEN SQUARE" header, append "(see Figure G-6 for

geographical depiction)" to the "Identifier: MMM - Marsden square line." Add the following figure at end of the

appendix:

Figure G-6. Marsden Square Reference Diagram

4) In Part A section of current Table G-6 under the "MAXIMUM WIND DATA" header, append "Report 77PnPnPn

as 77999 when maximum wind data has not been observed." to "Identifier: 77 – Indicator that data for maximum wind

level and for vertical wind shear follow when max wind does not coincide at flight. If the maximum wind level

16

Action

Recommended:

Status:23Feb17

Status:14Mar17

Status:21Mar17

Status:06Apr17

coincides with flight level encode as 66."

5) Propose to possibly revise or enhance legacy reference materials regarding the TEMP DROP code message in

Appendix G for future NHOP editions.

Review at the WG-HWSOR meeting. If approved, WG staff edits Appendix G, as recommended.

Received clarification from submitters.

ADOPTED.

Sent updated App G to submitter as agreed by submitter for editing. Expect rev 02 Apr.

Received updated Appendix G/posted.

10 Title

Submitter

Submitted

Discussion

Recommendation

Action

Recommended

Status:14Mar17

CARCAH Pre-Mission Coordination Responsibilities Listed in the NHOP Chapter 6

John Pavone, Warren Madden, and Steve Feuer, CARCAH

9 February 2017

Para. 6.1.4.2 in Chapter 6 of the NHOP lists five pre-mission coordination procedures for the CARCAH unit.

However, CARCAH does not perform the task listed in the second bullet, "Submitting a request for a WRA NOTAM

when necessary" nor the task listed in the fourth bullet, "For unscheduled missions, notifying the flying units and the

ATCSCC."

Eliminate the second and fourth bullet items under para. 6.1.4.2. Also,fix the paragraph title to read "Chief, Aerial

Reconnaissance Coordination, All Hurricanes (CARCAH)."

Review at WG-HWSOR meeting. If approved, WG staff edits Chapter 6 per recommendation above.

ADOPTED.

11 Title

Submitter

Submitted

Discussion

Recommendation

Revision of NHOP CHAPTER 6

FAA (AJR-22 John Kehler), NOAA AOC, and 53rd WRS

13 February 2017

The changes being submitted are from the NHOP Working Group. The NHOP Working Group is made up of FAA,

NOAA and 53rd representatives. Specifically, the changes: (1) better defines the WRA and the aircraft commander’s

responsibilities, (2) provides NOAA with the option of using an Unmanned Aircraft System (UAS) and spells out

those requirements, and (3) minor wording changes to make CHAPTER 6 more readable.

Changes to CHAPTER 6 for 2017 are highlighted in yellow:

1. Changed “Airspace” to “Aircraft” in the title of Chapter 6:

CHAPTER 6

AIRCRAFT OPERATIONS

2. Deleted WRA acronym if the paragraph title and added it at the end of the subparagraph:

6.1.2. WEATHER RECONNAISSANCE/RESEARCH AIRCRAFT (deleted WRA) .

17

6.1.2.1. Participating Aircraft. A “Participating Aircraft” for the purposes of the NHOP and related

documents1 is defined as a NOAA AOC or 53rd WRS manned aircraft listed in the Tropical Cyclone Plan of the Day

(TCPOD) or tasked with an unscheduled operational mission that is conducted in a Weather Reconnaissance Area

(WRA).

3. Changed NOTE to paragraph 6.1.2.3:

6.1.2.3. Unmanned Aircraft Systems (UAS) Operations. Unmanned Aircraft Systems (UAS)

operations are permitted with manned aircraft within a WRA as described in paragraph 6.2.3.7. No other UAS

operations are permitted in a WRA.

4. Added additional sentence to the end of the definition of a WRA:

6.1.3.2. Weather Reconnaissance Area. A Weather Reconnaissance Area (WRA) is airspace with defined

dimensions and published by Notice to Airmen (NOTAM), which is established to support weather

reconnaissance/research flights. ATC services are not provided within WRAs.2 Only participating weather

reconnaissance/research aircraft from NOAA AOC and 53rd WRS are permitted to operate within a WRA. A WRA

may only be established in airspace within U. S. Flight Information Regions (FIRs) outside of U.S. territorial airspace.

5. Changed 2 hours to 1 hour and added a NOTE:

6.1.4. PRE-MISSION COORDINATION.

6.1.4.1. Mission Coordination Sheet. All missions must provide a Mission Coordination Sheet

to the ATCSCC and the affected en route ATC facilities, as soon as possible, but no later than 1 hour prior to departure

time (see Appendix L).

NOTE- Every effort will be made to accommodate release of SUA. However, in some cases, SUA

will not be available for release. SUA Using Agencies determine if Department of Defense (DOD)

operational requirements are compatible with the establishment of a WRA and should define de-

confliction procedures for SUA that may not be released.

6. Deleted “Submitting a request for a WRA NOTAM when necessary” from paragraph 6.1.4.2. The CARCAH does

not do that function.

7. Deleted “when necessary” from the second bullet in paragraph 6.1.4.3.

6.1.4.3. 53rd WRS and NOAA AOC.

Submit the Mission Coordination Sheet (see Appendix I) according to sub-paragraph

6.1.4.1.

Submit a request to the appropriate FAA en route ATC facility for a WRA NOTAM.

8. Changed “expendables” to “weather instruments” and “deployed” to “released”:

6.1.4.4. Flying Agencies (other than the 53 WRS or NOAA AOC).

Issue advance notification to CARCAH of all planned reconnaissance/research missions

in areas where NHOP operations are being conducted, including proposed flight tracks,

aircraft altitudes, and locations where weather instruments may be released; this

information can be e-mailed to ncep.nhc.carcah@noaa.gov or faxed to 305-553-1901

(please indicate “CARCAH” on submitted materials).

9. Changed 2 hours to 1 hour:

6.1.5.2. ATCSCC Procedures.

Review the Mission Coordination Sheet (see Appendix L). Prepare a public Flow

Evaluation Area (FEA) based on the latitude/longitude points specified in the Mission

Coordination sheet when a mission is scheduled to be flown. The FEA naming

convention is the aircraft call sign. Modify the FEA when requested by the affected

facilities. (The flying unit will submit their Mission Coordination Sheet to the ATCSCC

and the affected en route ATC facilities at least 1 hour prior to flight departure time).

10. Changed 2 hours to 1 hour:

6.1.5.3. En Route ATC Procedures

Review the Mission Coordination Sheet (see Appendix L) - the flying unit will submit

2 The FAA may provide ATC services to participating flights in transit to and from WRAs, but will not provide ATC services, specifically

including separation, to these flights within a WRA.

18

their Mission Coordination Sheet to the ATCSCC and affected en route ATC facilities at

least 1 hour prior to flight departure time.

11. Changed “nm” to “NM” and reworded last sentence to make it more clear:

6.2.2. NHOP MISSIONS OUTSIDE A WRA.

6.2.2.1. International Airspace. International airspace is defined as the airspace beyond a

sovereign State’s 12 NM territorial sea limit. Beyond this limit ICAO rules apply. In international airspace, VFR flight

is not allowed at night. In class A controlled airspace, aircraft must operate using IFR procedures: ATC separation is

provided between IFR aircraft. In class E controlled airspace, both VFR and IFR operations are allowed; separation is

provided between IFR aircraft but only traffic and terrain advisories are provided to VFR traffic.

12. Changed “arranging” to “situating” and “flight” to “aircraft”:

6.2.2.4. Operations in Uncontrolled Airspace (Class F and G). Per FAA Order 7110.65, ATC

is not authorized to assign altitudes in nor provide separation between aircraft in uncontrolled airspace. While in

uncontrolled airspace, the aircraft commander is the IFR clearance authority. In addition, aircrews are responsible for

maintaining their own separation from the surface of the sea, obstacles, and oil platforms while operating below the

Minimum IFR Altitude (MIA). In class F and G uncontrolled airspace, both VFR and IFR operations are allowed.

When operating in uncontrolled airspace, flight information service, which includes known traffic information, is

provided and the pilot is responsible for situating the aircraft to avoid other traffic (ICAO, Annex 11).

13. Changed “nm” to “NM”:

6.2.3.1. General Operations. The airspace within a WRA is normally at or below FL150 with a radius of 200 NM

around a set of center coordinates. An ATC facility prevents non-participating aircraft receiving ATC services from

entering the WRA during the effective time of the WRA as published in the NOTAM. This area can include the

terminal areas (Class D Airspace) depicted on the NHOP Operational Maps (see Appendix K), and any other airspace

within 50 NM of the CONUS shoreline after radio contact is established with ATC. If not in radar contact within the

area as shown on the NHOP Operational Maps (see Appendix K), the aircrew will make position reports in relation to

designated navigational aids as requested by ATC along the coast. Any changes to the WRA will be coordinated with

the primary ARTCC.

14. Changed “MHZ” to “MHz” and “block altitude” “block of altitudes”:

6.2.3.3. Participating Aircraft Procedures in a WRA. The following actions must be taken by

the aircrews to de-conflict operations and enhance situational awareness with other participating aircraft within the

WRA:

Set 29.92 (inches Hg) in at least one pressure altimeter per aircraft.

Contact (Primary: VHF 123.05 MHz, Secondary: UHF 304.8 MHz, Back-up: HF 4701

KHz) the other participating aircraft and confirm (as a minimum) the pressure altitude,

location relative to a center point position, true heading, and operating altitude or block

of altitudes.

15. Added “UASs” as a weather instrument example and added a last sentence that provides additional requirements

for release or activation of weather instruments:

6.2.3.7. Weather Instrument Release in a WRA. The aircraft commander is the sole responsible

party for all weather instrument releases or sensor activations. Aircraft commanders will ensure coordination

with other participating aircraft prior to release or activation. (Examples of weather instruments are

dropsondes, UASs, and oceanographic profilers (OP)). When UAS weather instruments are released or

activated within a WRA: (a) only a single participating aircraft conducting the UAS weather instrument

release is permitted to operate within the WRA, and (b) the aircraft commander is responsible for ensuring

no other participating aircraft are operating in the WRA.

16. Changed “center(s)” to “facilities”; reworded last sentence of first subparagraph to make it more clear; and

changed “MHZ” to “MHz”:

6.2.5.3. Release of Dropsondes. During NHOP missions and when operationally feasible,

dropsonde instrument releases from FL 190 or higher and sensor activation must be coordinated with the

appropriate en route ATC facility by advising of a pending drop or sensor activation about 10 minutes prior

to the event when in direct radio contact with ATC. When ATC has radar contact with the aircraft, they will

notify the aircrew of any known traffic below them that might be affected. The aircraft commander is solely

responsible for release of the instrument after clearing the area by all means available.

When contact with ATC is via ARINC, event coordination must be included with the

position report prior to the point where the action will take place, unless all instrument

19

Recommended

Action:

Status:14Mar17

Status:21Mar17

Status:23Mar17

Status:27Mar17

release points have been previously relayed to the affected ATC facilities. Contact

between participating aircraft must be made using the frequencies listed in the second

bullet of paragraph 6.2.1.8.

During NHOP missions, approximately five (5) minutes prior to release the aircrew

will broadcast in the blind on radio frequencies 121.5 MHz and 243.0 MHz to advise any

traffic in the area of the impending drop. Pilots must not make these broadcasts if they

will interfere with routine ATC communications within the vicinity of an ATC facility.

The aircraft commander is responsible for determining the content and duration of a

broadcast, concerning the release or sensor activation.

Review at WG-HWSOR meeting and edit Chapter 6 if approved.

AGREED AT MEETING WG-HWSOR. 14Mar17

Received signed MOA NOAA-53rd WRS-FAA ATO in support of NHOP.

Received revised version dtd 03 03 17.

Sent MOA and revised Chapter 6 to EM

Chapter 6 posted for review.

12 Title

Submitter

Submitted

Discussion

Recommendation

Action

Recommended

Status:14Mar17

Status:20Mar17

Status:21Mar17

NHOP Administrative Change

Steve Feuer, CARCAH

14 February 2017

The NHOP contains several references to the Air Force Weather Agency (AFWA). However, on 27 March 2015, it

was renamed as the 557th Weather Wing (557 WW).

Update content in the publication to reflect the name change, replacing “Air Force Weather Agency” with “557th

Weather Wing” and “AFWA” with “557 WW.” Instances include:

second sentence of para. 4.3.1

second sentence of para. 5.9.1

first, third, and last sentence of para. 5.9.3.2

sixth sentence of para. 7.1.6

first sentence of para. 7.4

items 1 and 3 under the “Products” column for the DMSP entry in Table 7-2

Appendix I telephone number listing

Appendix M list of acronyms and abbreviations

Review at WG-HWSOR meeting. If approved, edit Chapters 4, 5, 7, and Appendices I and M accordingly.

ADOPTED.

Requested clarification -- where to input “557th Weather Wing” in Appendix M. Added “WW” in Appendix M

for “Weather Wing” under “W”. Posted.

13 Title

Submitter

Submitted

Discussion

Revision of NHOP to specify the requirement for ocean observations

CAPT Sanabia (USNA), CAPT Gabriel (OPNAV N2N6E NAVDEPNOAA), and LCDR Mansour (OPNAV N2N6E

NAVDEPNOAA).

17 February 2017

Oceanographic observations collected during 53rd WRS WC-130J Hurricane Reconnaissance missions have been

shown to consistently improve initial conditions and forecasts in the NCOM and HYCOM ocean models. The

observations have also been shown to improve coupled model track and intensity forecasts in the coupled COAMPS-

TC model. As such, these observations impact Fleet operations and are essential to maximize operational readiness as

20

Recommendation

well as the safety of forces afloat and ashore. The Oceanographer of the Navy has directed the submitters of this

action item to request the WG-HWSOR to consider incorporating into the NHOP the collection of these ocean

observations as part of regularly tasked tropical cyclone reconnaissance missions, to include A-sized buoy

deployments at transit altitudes.

Change 9.1.3 as follows:

9.1.3. Drifting Buoys and Airborne Expendable Bathythermographs (AXBTs).

9.1.3.1. NDBC. NDBC is capable of acquiring, preparing, and deploying drifting buoys; however, an operational

drifting buoy requirement has not been identified or funded. NDBC receives Navy buoy and AXBT data from

observations collected during some WC-130J missions via NAVO-NDBC communications channels. NDBC verifies

formatting and uploads the observations to the Global Telecommunications System (GTS).

9.1.3.2. Navy. Since 1998, the Naval Oceanographic Office (NAVOCEANO) has deployed meteorological and

oceanographic drifting buoys to report surface meteorological and oceanographic measurements for operational

purposes, as tropical systems move through data sparse regions tracking toward the U.S. coastline. Additionally, Navy

A-sized buoys (primarily AXBTs and ALAMO floats, which are tube launched and therefore do not require lowering

the WC-130J aircraft ramp during flight) are often deployed by the 53rd WRS and can be deployed NOAA AOC during

operational tropical cyclone reconnaissance missions. Buoy measurements improve ocean forecast model initialization

and are a source of supplemental data providing tropical forecasters information on storm characteristics. Once

deployed, drifting buoys typically have a life span of 1 to 2 years, while the AXBTs are single use instruments. All

data are available through standard World Meteorological Organization (WMO) data sources. NAVOCEANO

acquires, prepares, and deploys drifting meteorological and oceanographic buoys based on operational requirements

identified by the Commander, U.S. Fleet Forces Command (COMUSFLTFORCOM). Currently,

COMUSFLTFORCOM has identified the Navy’s drifting buoy support as a standing requirement to support fleet

safety, assist in fleet sortie decisions particularly in the Norfolk, VA and Jacksonville, FL fleet concentration areas, and

enhance tropical weather preparedness.

9.2. Requests for Buoy Deployment.

Drifting buoy deployments involving ramp-deployed instruments (which impact flight path planning) should be

coordinated through the Department of Commerce (DOC), National Oceanic and Atmospheric Administration

(NOAA). Deployments will be requested through HQ Air Force Reserve Command (AFRC). Deployments in advance

of a U.S. land-threatening hurricane require a 36- to 48-hour notification.

Deployments using the A-sized launch tube will be coordinated between buoy providers (NAVOCEANO, USNA and

NOAA HRD) and aircraft operators (53rd WRS and NOAA AOC). Buoy providers will arrange pre-season acquisition

and airfield staging of the A-sized buoys. Deployment planning will occur during routine pre-flight mission briefings

and do not require notation in the TCPOD. Deployments will be on a not-to-interfere basis with primary

reconnaissance mission tasking. Navy-provided A-sized buoys will only be deployed when buoys are available and

primary mission tasking allows. There is no requirement for an AXBT or ALAMO backup deployment capability in

the event of launcher casualty or aircraft unavailability. Buoys may be deployed both in transit and in the alpha pattern

without altitude restriction.

9.2.1. CARCAH.

CARCAH will issue, through the Tropical Cyclone Plan of the Day (TCPOD), an alert or outlook for drifting buoy

ramp-deployment 48 hours before the planned deployment. Hard tasking for the deployment will be issued via the

TCPOD at least 16 hours, plus flying time to the deployment location, before the event. Deployments of A-sized

buoys (including tube-launched AXBTs and ALAMO floats) do not require notations in the TCPOD.

9.2.2. Deployment of DOC Buoys.

DOC may request the deployment of a drifting buoy and subsurface float array with up to 40 elements at a distance of

200 to 400 nm from the storm center, depending on the dynamics of the storm system. DOC will ensure the buoys and

mission-related DOC personnel are delivered to AFRC. The specific DOC request for placement of the buoys will

depend on several factors, including:

Characteristics of the storm, including size, intensity, and velocity.

Storm position relative to the coast and population centers.

Availability of aircraft and Loadmasters (LM) certified for buoy deployment.

9.2.3. Deployment Position.

The final deployment position will be provided before the flight crew briefing. An example of a possible buoy and

float deployment pattern from the recent CLBAST Experiment is shown in Figure 9-1.

21

Action

Recommended:

Status:03mar2017

Status: 06Mar17

Status: 14Mar17

Status:28Mar17

Status:31Mar17

53rd WRS, USNA, NAVOCEANO, and NDBC will coordinate operational details for 2017 season as in past seasons.

USN/USAFR MOA in development to standardize operations in out years.

Review at WG-HWSOR meeting. If approved, WG staff edits NHOP Chapter 9 accordingly.

Requested clarification from submitters regarding various questions from the WG staff about this AI including

relationship to AXBTs and previous related informational items, requirements, taskings, resources, and dataflow.

Update language received today from submitters. Amended language in “Discussion” and section 9.2.2. By way of

clarification, “A-size buoys” include AXBTs, thus establishing continuity with earlier informational items received on

this subject. Received revised section 9.2. /DM

Who/when/how are the proposed actions to be done? Need a new appendix? How does this work in real-time?

Submitters will provide updated language clarifying program execution/roles. Will try this year’s NHOP. WG

will review updated language.

Revised Recommendations received. Section 9.2.3 unchanged from previous AI entry.

AOC consulted by submitters, with concurrence obtained.

14 Title

Submitter

Discussion

Recommendation

Action:14Mar17

Action: 20Mar17

Change to 5.2.1.3 in NHOP to 3 deployed locations

Kaitlyn Woods, Lt Col 53rd WRS

Currently 5.2.1.3 in the NHOP reads "Maintaining the capability of operating from two (2) deployed locations, as well

as from home station, simultaneously." This sentence drives our mission kit supply, meaning AFRC will only fund

two kits. The need arises at least once a year to operate

from three separate locations and we require a third kit. Recommend changing 5.2.1.3 to read "Maintaining the

capability of operating from three (3) deployed locations, as well as from home station, simultaneously."

Change wording for 5.2.1.3 from “two (2) deployed locations” to “three (3) deployed locations”.

ADOPTED.

Entered into Ch5.

15 Title

Submitter

Discussion

Recommendation

Recommendation

CPHC changes to 2017 NHOP

Tom Evans, CPHC

Section 2.2.2

Central Pacific Ocean (north of the equator between 140°W and 180°). Advisories are the responsibility of the

Director, Central Pacific Hurricane Center (CPHC), Honolulu, HI. In addition to the main Hawaiian Islands, CPHC

also issues watches and warnings for Johnston Atoll, Palmyra Atoll, Midway, and the northwest Hawaiian Islands. The

CPHC will consult with JTWC prior to issuing initial and final advisories and prior to issuing any advisory that

indicates a significant change in forecast of intensity or track from the previous advisory. Exchange of information is

encouraged on subsequent warnings when significant changes are made or otherwise required. The CPHC will notify

JTWC prior to issuance of a Special Tropical Weather Outlook (TWO)

Section 3.2.1

NHC and CPHC prepare text and graphical versions of the TWO during their respective tropical cyclone seasons. The

TWO covers tropical and subtropical waters and discusses areas of disturbed weather and the probability of tropical

22

Recommendation

Recommendation

Recommendation

Recommended

Action

Status:14Mar17

Status: 20mar17

Status:24mar17

cyclone development. The NHC outlook, covering the next 120 hours, will mention tropical cyclones and subtropical

cyclones, including the system's location (in either general terms or map coordinates), status, and change in status. The

CPHC outlook, covering the next 120 hours, will mention tropical cyclones, including the system’s location (in either

general terms or map coordinates), status, and change in status.

Section A.2.1

WFOs with coastal county responsibilities and selected inland WFOs will issue these products which are intended to

communicate important information to media, local decision makers, and the public interested in a bigger picture on

present and anticipated storm effects in their county warning area (CWA). The HLS contains a succinct overview of

the tropical event and a generalized summary of potential impacts and preparedness information for land areas only.

Potential impact information is ordered based upon the greatest expected impact within the entire CWA. Possible

sections are wind, surge, flooding rain, tornadoes, and other coastal hazards.

Section 7.2.2.2

Satellite Interpretation Messages. WFO Guam issues these discussions two times a day to describe synoptic features

and significant weather over the Micronesian waters.

Table 3-5

Remove Satellite Interpretation Message for PHFO.

Edit Chapters 3 and 7, and Appendix A accordingly, as approved by the WG-HWSOR.

Discuss at WG-HWSOR and edit NHOP as approved.

ADOPTED.

Requested clarification from CHPC re: Section 7.2.2.2. Other changes entered in Chs. 3, 7, and App A.

Received – 20Mar2017 version Ch7.2.2 is correct.

16 Title

Submitter

Discussion

Recommendation

CPHC changes to 2017 NHOP Section 3.2.8 Tropical Cyclone Watch Warning Product (TCV)

Tom Evans, CPHC and Jessica Schauer, NWS/Tropical Program Lead

This section currently describes the national TCVs. The NWS now issues local TCVs from coastal Weather Forecast

Offices. Should these local TCVs be included in the NHOP? If so, wording to include in the NHOP should be taken

from the National Weather Service instructions (NWSI 10-601, Sections 1.7 and 7.1:

http://www.nws.noaa.gov/directives/sym/pd01006001curr.pdf).

Alter section 3.2.8 to include the local TCV.

The national TCV is based upon the Valid Time Event Code (VTEC). It summarizes all new, continued, and cancelled

tropical cyclone watches and warnings issued by the NHC for the U.S. Atlantic and Gulf coast, southern California

coast, Puerto Rico, and U.S. Virgin Islands. In the Atlantic, the NHC-issued TCV also contains the inland VTEC

provided by NWS Weather Forecast Offices (WFOs). The CPHC will issue a TCV for the main islands of the State of

Hawaii. The product is issued each time a U. S. tropical cyclone watch and/or warning is issued, continued, or

discontinued for all Atlantic, portions of the North East Pacific, and the North Central Pacific Ocean basin tropical

cyclones.

The local TCV text product is a segmented, nearly automated, VTEC product with each segment being a discrete

forecast zone. It is issued by coastal Weather Forecast Offices (WFOs) in the Atlantic and North Central Pacific

basins. Each segment contains land-based tropical cyclone watches / warnings in effect, meteorological information,

threats (Wind, Storm Surge, Flooding Rain, Tornadoes) and their potential impacts. The product is generated from

23

Recommended

Action

Status:14Mar17

Status:20Mar17

Status:21Mar17

local gridded forecast information and national guidance and is, therefore, not intended to be manually edited by the

forecaster. This text product is intended for parsing by the weather enterprise, and is paired with the WFO Hurricane

Local Statement (HLS) to provide a complete, localized tropical forecast. It can also be useful to decision makers as it

provides detailed information on timing, threats, and impacts on a zone level.

Review at WG-HWSOR. Edit section 3.2.8 accordingly if approved by the WG-HWSOR.

ADOPTED.

Entered into Ch3.

Received correction to add the following sentence in 3.2.8: In the Atlantic, the NHC-issued TCV also contains the

inland VTEC provided by NWS Weather Forecast Offices (WFOs)

17 Title

Submitter

Date Submitted

Discussion

Recommendation

Recommended

Action

Status:14Mar17

Status: 28Mar17

The 2017 version of the WSR-88D TCOP (Tropical Cyclone Operations Plan) for Build 17.X to be added to the

NHOP page.

Chris Huffer, ROC (Radar Operations Center)

8 March 2017 with revision (planned) for 28th March 2017

The 2017 version of the TCOP Build 17.X is written for Radar sites that have been updated and are currently running

on Build 17. Otherwise, Radar sites that remain on 16.1 will use the 2016 version of TCOP.

If the WSR-88D Radar site is on Build 16.1, then they will be using the 2016 edition of the TCOP and 16.1 Quick

Check List. If the Radar site is on Build 17.X, then they will use the 2017 edition of the Build 17.X TCOP and 17.X

Quick Check List.

Discuss at WG-HWSOR and edit NHOP accordingly if approved.

OPEN. WILL DISCUSS AT A 2ND MEETING.

WSR-88D Tropical Cyclone Plan listed in http://www.ofcm.gov/publications/nhop/nhopreview.htm

24

Informational Items from NWS/HQ for 71th IHC/TCRF

I.1 Title

Submitter

Submitted

Discussion

Recommendation

INFORMATIONAL ITEM: Changing NWS criteria for issuing tropical cyclone watches and

warnings to include certain land-threatening disturbances that are not yet tropical cyclones

Jessica Schauer, NWS Tropical Program Leader

3 February 2017

Beginning on or about May 15, 2017 pending final approval, the National Weather Service (NWS) will

have the option to issue watches, warnings, and graphical and textual advisory products for disturbances

that are not yet a tropical cyclone, but which pose the threat of bringing tropical storm or hurricane

conditions to land areas within 48 hours. Under previous long standing NWS policy, the NWS has not been

permitted to issue a hurricane or tropical storm watch or warning until after a tropical cyclone had

formed. Advances in forecasting over the past decade or so, however, now allow the confident prediction

of tropical cyclone impacts while these systems are still in the developmental stage. For these land-

threatening “potential tropical cyclones”, the NWS will now issue the full suite of products that previously

has only been issued for ongoing tropical, subtropical, or post-tropical cyclones. In addition, the NWS will

begin issuing watches and warnings for storm surge associated with tropical cyclones threatening the

Atlantic and Gulf coasts of the contiguous United States in 2017, and will have the ability to issue these

watches and warnings for potential tropical cyclones as well. The Potential Storm Surge Flooding Map and

Prototype Storm Surge Watch/Warning graphic would be issued for these systems when appropriate.

Potential tropical cyclones will share the naming conventions currently in place for tropical and subtropical

depressions, with depressions and potential tropical cyclones being numbered from a single list (e.g.,

“One”, “Two”, “Three”, ..., “Twenty-Three”, etc.). The assigned number will always match the total

number of systems (tropical cyclones, subtropical cyclones, or potential tropical cyclones) that have

occurred within that basin during the season. For example, if three systems requiring advisories have

already formed within a basin in a given year, the next land-threatening disturbance would be designated

“Potential Tropical Cyclone Four”. If a potential tropical cyclone becomes a tropical depression, its

numerical designation remains the same (i.e., Potential Tropical Cyclone Four becomes Tropical

Depression Four).

The issuance times for potential tropical cyclone products will be identical to the standard tropical cyclone

product issuance times. NWS products for potential tropical cyclones will be issued until watches or

warnings are discontinued or until the wind and storm surge (if applicable) threat for land areas sufficiently

diminishes, at which point advisories would be discontinued. However, if it seems likely that new watches

or warnings would be necessary within a short period of time (say 6-12 hours), then advisories could briefly

continue in the interest of service continuity. Once a system becomes a tropical cyclone, the normal rules

for discontinuing advisories will apply. Potential tropical cyclone advisories will not be issued for systems

that pose a threat only to marine areas.

Because NHC and the Central Pacific Hurricane Center will be issuing their normal graphical products

depicting the five-day forecast track and uncertainty cone for potential tropical cyclones, to avoid potential

confusion the Graphical Tropical Weather Outlook will no longer display a formation area for these

systems.

If the NWS decides to proceed with issuing tropical cyclone watches and warnings for potential tropical

cyclones for the 2017 hurricane season, a Service Change Notice will be issued to announce the change.

INFORMATIONAL ITEM

25

I.2 Title

Submitter

Submitted

Discussion

INFORMATIONAL ITEM: The Addition of Tropical Cyclone Storm Surge Watches and Warnings

for the Atlantic and Gulf Coasts of the Contiguous United States

Jessica Schauer, NWS Tropical Program Leader

3 February 2017

Effective on or around June 1, 2017, the National Weather Service (NWS) will implement new Storm

Surge Watches and Warnings in association with Atlantic basin tropical cyclones (i.e., hurricanes, tropical

storms, and tropical depressions), subtropical cyclones, or post-tropical cyclones affecting the contiguous

United States. The new Storm Surge Watches and Warnings will be integrated into the current NWS

product suite, including all applicable tropical cyclone graphical and textual advisory products.

Definitions for the Storm Surge Watch and Warning are provided below:

Storm Surge Watch: The possibility of life-threatening inundation from rising water moving inland from

the shoreline somewhere within the specified area, generally within 48 hours, in association with a tropical

cyclone, a subtropical cyclone, or a post-tropical cyclone. The watch may be issued earlier when other

conditions, such as the onset of tropical-storm-force winds, are expected to limit the time available to take

protective actions for surge (e.g., evacuations). The watch may also be issued for locations not expected to

receive life-threatening inundation, but which could potentially be isolated by inundation in adjacent areas.

Storm Surge Warning: The danger of life-threatening inundation from rising water moving inland from the

shoreline somewhere within the specified area, generally within 36 hours, in association with a tropical

cyclone, a subtropical cyclone, or a post-tropical cyclone. The warning may be issued earlier when other

conditions, such as the onset of tropical-storm-force winds, are expected to limit the time available to take

protective actions for surge (e.g., evacuations). The warning may also be issued for locations not expected

to receive life-threatening inundation, but which could potentially be isolated by inundation in adjacent

areas.

Storm Surge Watches or Warnings will not be issued for the Pacific hurricane basin or WFO San Juan’s

area of responsibility until further notice.

Coastal Flood Watches, Warnings, and Advisories will continue to be issued for flooding of coastal areas

associated with storms that are not tropical cyclones, subtropical cyclones, or post-tropical cyclones. Most

frequently, they will be issued for winter storms, unusually high tides, or prolonged periods of strong

onshore winds that have pushed water into places it does not normally go. Coastal Flood Advisories may

be issued in areas adjacent to a Storm Surge Watch or Warning to alert for potentially dangerous coastal

flooding that is below the threshold established by the National Weather Service for life-threatening

inundation.

Changes to the Hurricane Local Statement (HLS) product to reflect Storm Surge Watches or Warnings

issued by Weather Forecast Offices (WFOs) will be limited to the "NEW INFORMATION" section of the

product. The subsections for "CHANGES TO THE WATCHES AND WARNINGS" and "CURRENT

WATCHES AND WARNINGS" will include Storm Surge Watches or Warnings when condition warrant.

National Hurricane Center (NHC) Tropical Cyclone Public Advisory (TCP) products will now list Storm

Surge Watches and Warnings, as applicable, under the “WATCHES AND WARNINGS” section and more

detailed information about the storm surge hazard will be provided in the “HAZARDS AFFECTING

LAND” section. Storm Surge Watches and Warnings will be listed in the “SUMMARY OF WATCHES

AND WARNINGS IN EFFECT” section of the Tropical Cyclone Forecast/Advisory (TCM) product.

In addition, the Storm Surge Watch/Warning Graphic previously issued by NHC as a prototype will

become operational at the start of the 2017 Atlantic hurricane season. Because Storm Surge Watches and

Warnings are issued on a grid rather than for entire NWS zones or for entire counties, users are highly

encouraged to use the Keyhole Markup Language (KML) files available on the NHC website, rather than

the Valid Time Event Code (VTEC), to obtain the most accurate depiction of the area under a Storm Surge

26

Watch or Warning.

All Tropical Cyclone Watch/Warning (TCV) products issued by NHC and WFOs for tropical cyclones,

subtropical cyclone, and post-tropical cyclones affecting the Atlantic and Gulf coasts of the contiguous

United States will include VTEC for Storm Surge Watches and/or Warnings when conditions warrant. The

following VTEC phenomenon and significance codes will be used:

SS.A - Storm Surge Watch

SS.W - Storm Surge Warning

Examples of the WFO and NHC issued TCV products with the new Storm Surge Watches and Warnings

can be viewed at:

www.nhc.noaa.gov/experimental/tcv

VTEC will continue to be used to activate some dissemination systems, such as NOAA Weather Radio All-

Hazards (NWR). While users are highly encouraged to use the KML files to display Storm Surge Watches

and Warnings, the NWS also recognizes that many users rely on VTEC to parse and disseminate

information. VTEC users should be aware the geographical area associated with a Storm Surge Watch or

Warning using VTEC will be larger than the actual area of the watch or warning as depicted by the gridded-

based forecast.

Beginning in the 2017 hurricane season, the NWS may request Emergency Alert System (EAS) and

Wireless Emergency Alert (WEA) activation for the Storm Surge Warning. In most jurisdictions, the NWS

will not request EAS or WEA activation for the Storm Surge Watch. Specific details about changes to the

EAS for your area will be provided by your local WFO in Public Information Statements, on WFO web

pages, and over NWR. Broadcasters should note that if EAS equipment is not updated and the WFO

requests EAS activation with the new event code(s), EAS encoder/decoder equipment will usually decode

the information received as an “UNKNOWN” event code.

Storm Surge Watches and Warnings will be broadcast over NWR. Current NWR receivers providing a

limited, caption-like message display will likely show wording such as "UNKNOWN WATCH" or

"UNKNOWN WARNING". Receivers equipped with Special Area Message Encoding (SAME) capability

and properly programmed should automatically turn on for counties affected by a Storm Surge Watch or

Warning. The 1050-Hz Warning Alarm Tone (WAT) will generally be used for the Storm Surge Warning

but will not be used for the Storm Surge Watch.

Pending operational approval, the NWS will also issue storm surge watches and warnings for potential

tropical cyclones beginning on or around June 1, 2017. A potential tropical cyclone is a disturbance that is

not yet a tropical cyclone, but one for which the NWS will begin issuing tropical cyclone watches or

warnings because it poses the threat of bringing tropical storm or hurricane conditions or life-threatening

tropical cyclone storm surge inundation to land areas within 48 hours. If the NWS decides to proceed with

issuing tropical cyclone watches and warnings for potential tropical cyclones for the 2017 hurricane season,

a Service Change Notice will be issued to announce the change.

INFORMATIONAL ITEM

I.3 Title

Submitter

Submitted

Discussion

Probabilities of Significant Wave Heights in Tropical Cyclones

Chris Landsea – National Hurricane Center

11 Jan 2017

This informational item provides an update through March 2017 about progress thus far on this potential

new public product for the marine community.

Originally Submitted for 2016 Meeting:

27

The National Hurricane Center currently provides probabilistic guidance to the public on a range of

phenomenon: tropical cyclone genesis, tropical cyclone wind speed probabilities, and storm

surge probabilities. One tropical cyclone related feature that often causes damaging and life-threatening

conditions over the open oceans are large oceanic waves. Steep, short-period, tall waves - commonly

occurring in hurricanes - striking a ship broadside are most dangerous. Unfortunately, there are examples

of ships encountering severe wave conditions within hurricanes and suffering disastrous results (the

Fantome in 1998's Hurricane Mitch, the Bounty in 2012's Hurricane Sandy, and most recently the El Faro

in 2015’s Hurricane Joaquin being the most infamous).

Currently, NHC (through the Hurricane Specialist Unit) issues a quadrant-based analysis of the current

radial extent of 12' seas. (The height here refers to the significant wave height, which is the

average height of the highest one-third of the waves experienced at a particular

location. Individual waves may be more than twice the significant wave height.) NHC also

provides wave height forecasts (through the Tropical Analysis and Forecast Branch), which are expressed

deterministically out through six days and available in text, graphical, and gridded formats. These are

provided by TAFB not only when active tropical cyclones are occurring but the remainder of the year as

well for NHC's area of responsibility (eastern tropical Pacific Ocean, tropical North Atlantic Ocean, Gulf of

Mexico, and Caribbean Sea). Similarly, the Ocean Prediction Center and the Central Pacific Hurricane

Center provide similar text, graphical, and gridded wave height forecasts that include tropical cyclones for

their areas of responsibility.

However, such deterministic forecasts of wave heights during tropical cyclones do not take into account the

uncertainties of the predicted track, intensity, and size. Moreover, the lack of a tropical cyclone

specific wave height graphical product may diminish the visibility of existing NHC predictions.

Thus to fill this need, it is proposed to develop tropical cyclone focused Wave Height Probabilities. Such a

public product could be issued for active tropical cyclones with graphics depicting the likelihood

of wave heights exceeding two or three thresholds (say, 12' and 20', or 12', 18', and 24'). The output could

be expressed, like that for wind speed probabilities, in increments of 12 or 24 h, along with a 5 day

cumulative probability. See the below figure for how such output could be provided. Such new

information could be invaluable for mariners over the open ocean in making better decisions in and around

dangerous tropical cyclones.

Technically, the approach for such development of a new product is straightforward. Currently, one has

access to the wind fields of the 1000 simulated tropical cyclones as part of the Monte Carlo wind

speed probability program that is driven by the NHC deterministic tropical cyclone forecast. The wind field

from these 1000 simulated tropical cyclones can be used to drive an ensemble of wave models (perhaps a

simplified version of the Wave Watch III model) in which the wave height output can then be expressed

probabilistically for various wave height thresholds. (It is noted that there already exists wave

height probabilities from the GFS-ensemble runs of the Wave Watch III model. However, these are

currently not accurate enough for this purpose because of the lack of strong, inner core winds in the GFS-

ensemble members, lack of sufficient dispersion in the GFS-ensemble tracks, and lack of consistency with

the NHC official forecast.)

Currently, NOAA (at the NOAA Hurricane Conference in December) approved the concept to develop

Probability of Significant Wave Heights in Tropical Cyclones graphical products. A team has been

established within NOAA to formulate long-term plans needed to develop the products. Technical

development is anticipated to occur during 2017 and 2018.

28

INFORMATIONAL ITEM

29

OPEN ACTION ITEMS FROM PREVIOUS YEARS

70

-5

Title

Submitter

Submitted

Discussion

Recommendation

Action

Status:16Mar16

Status:9Feb17

Next Generation Vortex Message

Mike Dion, NWS Tropical Program Leader; James Franklin and Eric Blake, NHC

8 February 2016; rev9 Feb 2017

The current form of the Vortex Message (VDM) has limitations that detract from the VDM’s utility. Most

of these result from the historical emphasis on the inbound portion of the typical figure 4 pattern. Over

time, some additional information has been added to the remarks section of the VDM (Item P), but data

conveyed there are neither as complete nor as easily decoded as the regular coded items. This forces users

to work through the HDOB data to make sure important data haven’t been missed. For example, the

current VDM often does not include the maximum observed surface wind on an outbound leg, even when

the maximum outbound surface wind is greater than the maximum inbound value.

What we envision are modifications to the VDM to make it a more complete representation of the state of

the tropical cyclone vortex, and improve the consistency in the way key observations are reported.

Conceptually, we’d like to see a message that gives equal standing to outbound flight-level and surface

wind observations, and would like to move most of the information currently in the remarks to their own

dedicated line entries. We recognize that there is interest in conveying the center information as quickly as

possible, and therefore we may need to consider whether there should be “preliminary” and “final” versions

of the transmitted message.

Begin discussion involving Operational forecast centers (NHC) and aircraft operators (53rd WRS, AOC) on

how to improve the utility of the VDM, with the goal of presenting a specific proposal for an updated

message format to the 2017 Interdepartmental Hurricane Conference.

53WRS/Lt Col Woods, CPHC/Birchard, NHC/Blake, CARCAH/Steve F, AOC/Jim McFadden will

engage and bring proposal for next year. NHC leads. OFCM supports.

In coordination with all parties, we have a proposal for possible operational implementation during the

2018 hurricane season. The main changes consist of reorganizing the placement of the outlined items so

that they are more logically grouped together, adding an outbound maximum wind block, and making

observations that were previously stated in the VDM remarks section (old format Item P) permanent stand-

alone items. Specific changes include:

1) For Item B, the fix location is placed all on one line instead of two, and the latitude and longitude

coordinates are specified in decimal degrees instead of degrees-minutes.

2) A newly designated TC center data block comprises Items C through G. The central MSLP is reported

in Item D instead of Item H. Item E has the center dropsonde wind vector that was previously reported as a

remark; this would be encoded "NA" if the pressure in Item D is extrapolated or a dropsonde measurement

is not available, as well as in preliminary VDMs. Center/eye shape and size characteristic lines are moved

up to Items F and G from Items L and M.

3) The inbound maximum surface and FL wind block is shifted down to Items H through K from Items E

through G. Observation times are appended to the bearing and range location lines.

4) A new set of outbound maximum surface and FL wind lines are added as Items L through O. The format

and order is analogous to the inbound maximum wind block. The values would be encoded "NA" normally

for preliminary VDMs or if the observations are missing.

5) The temperature and dew point lines are shifted down to Items P through R from Items I through K, and

the fix characteristics lines are shifted down to Items S and T from Items N and O without any other

changes.

6) Remarks are shifted down to Item U from Item P. Outbound maximum FL wind and dropsonde surface

wind remarks are no longer needed since that information is contained in above items. However, the

maximum FL wind should always still be reported using the same criteria and rules previously established.

30

Recommended

Action:

Other designated remarks would appear on lines in this section without modification.

If approved, necessary adjustments will need to be made to Fig. 5-3, Table 5-2, and Fig. 5-4 in Chapter 5 of

the NHOP but probably not published until the season in which the new VDM is ready to go live (most

likely the 2018 season).

Example of Changes:

Old format:

URNT12 KNHC 241133

VORTEX DATA MESSAGE AL162016

A. 24/11:12:50Z

B. 10 deg 58 min N

082 deg 46 min W

C. 700 mb 2927 m

D. 90 kt

E. 144 deg 5 nm

F. 253 deg 78 kt

G. 158 deg 8 nm

H. 977 mb

I. 10 C / 3042 m

J. 18 C / 3045 m

K. NA / NA

L. CLOSED

M. C20

N. 12345 / 7

O. 0.02 / 1 nm

P. AF301 0616A OTTO OB 13

MAX OUTBOUND AND MAX FL WIND 108 KT 349 / 14 NM 11:17:00Z

CNTR DROPSONDE SFC WIND 210 / 11 KT

New format:

URNT12 KNHC 241133

VORTEX DATA MESSAGE AL162016

A. 24/11:12:50Z

B. 10.97 deg N 082.77 deg W

C. 700 mb 2927 m

D. 977 mb

E. 210 deg 11 kt

F. CLOSED

G. C20

H. 90 kt

I. 144 deg 5 nm 11:07:00Z

J. 253 deg 78 kt

K. 158 deg 8 nm 11:07:30Z

L. 95 kt

M. 314 deg 5 nm 11:17:30Z

N. 033 deg 108 kt

O. 349 deg 14 nm 11:17:00Z

P. 10 C / 3042 m

Q. 18 C / 3045 m

R. NA / NA

31

Status:14Feb17

Status:29Mar17

Status:6Apr17

S. 12345 / 7

T. 0.02 / 1 nm

U. AF301 0616A OTTO OB 13

MAX FL WIND 108 KT 349 / 14 NM 11:17:00Z

Not discussed due to time. Tabled for follow-up meeting.

Submitters clarify this change is not required for 2017 NHOP but anticipate action for next year.

Should WG approve in 2017 for 2018 publishing?

32

CLOSED ACTION ITEMS FROM PREVIOUS YEAR

ACTION ITEMS FROM 70TH IHC (2015)

70

-1

Title

Submitter

Submitted

Discussion

Recommendation

Status:16Mar16

Status:06Apr2016

Revision of NHOP 2015 Para. 5.7.8, Observation Numbering and Content

USAF/53rd WRS (Lt Col K.Woods) and Steve Feuer, CARCAH

14 March 2016 (Revised)

The first and last two sentences in the paragraph contain content that is either obsolete or no longer

applicable. The remaining content about observation numbering should be retained but better stated.

Change para. 5.7.8 as follows:

5.7.8. Observation Numbering and Content.

Air Force aircraft movement information (i.e., departure time and location, and ETA’s to locations) will

not be included in observation remarks. That information should be passed to CARCAH via SATCOM

administrative messages. The mission identifier will be the first mandatory remark followed by the

observation number. All observations (RECCO, vortex, dropsonde) from the first to the last will be

numbered sequentially. HDOBs will be automatically numbered sequentially but separately from other

observations. When an aircraft is diverted from its original mission to fulfill NHC requirements, conclude

the original mission by using the last report remark.

The next observation from the diverted aircraft will use the CARCAH-assigned mission 5-16 identifier,

will be numbered OB 01, and will include the time of diversion.

EXAMPLE

RMK AF306 0lBBA INVEST OB 01 DPTD AF306 WXWXA AT 05/1235Z

All aerial weather reconnaissance messages will contain the mission identifier followed by an observation

number as the first mandatory remark. Standard observation messages (RECCO, vortex, and dropsonde)

will be sequentially numbered in the order they are transmitted from the aircraft. The final message will

contain a "LAST REPORT" remark. High-density observation (HDOB) messages will also be numbered

sequentially but separately from the other messages.

Accepted. CLOSED UPON EDITING.

Section 5.7.8 edited as submitted.

70

-2

Title

Submitter

Submitted

Discussion

Miscellaneous Administrative Changes, Corrections, and Additions to the NHOP

Warren Madden and Steve Feuer, CARCAH

9 February 2016

14 March 2016 (Revised)

A. TEMP DROP Code Message Table G-6 in Appendix G

A minor correction needs to be made to the Standard Isobaric Surfaces section so that it is in accordance

with WMO 306 Vol. 1, p. A-195.

33

Recommendation

Discussion

Recommendation

Discussion

Recommendation

Status:16Mar201

6

Status:07Apr2016

For the "Identifier: h1h1h1” description, the third sentence should be changed to “Add 500 to the absolute

value of hhh for negative 1000 mb or 925 mb heights.”

B. Communications Headings for SAB Dvorak Analysis Products Table 7-1 in Chapter 7

The entries in the WMO heading and oceanic area columns are erroneously transposed for "North Indian"

and "TXIO" and for "South Indian" and "TXXS."

Switch the content in the columns.

C. HD/HA Data Line Format for HDOB Messages Table G-5 in Appendix G

A correction needs to be made to the description of the “XXXX” field regarding how negative D-values

are encoded.

The second to last sentence should be changed to “Negative D-values are encoded by adding 5000 to the

absolute value of the D-value.”

A, B, C adopted. CLOSED UPON EDITING NHOP.

Change A above entered in App G.

Change B above entered in Table 7-1.

Change C above entered in App G.

70

-3

Title

Submitter

Submitted

Discussion

Recommendation

Miscellaneous Administrative Changes, Corrections, and Additions to the NHOP Chapter 5 to

Adhere to USAF Doctrine Language

Lt. Cols. Kait Woods and John Talbot/53rd WRS USAFR

11 February 2016 and revised 01Apr2016 by Lt Col Talbot

There appears to have been an administration error last year and we need to change back paragraphs

5.5.1.1 and 5.5.3.1.1.1 below to the 2014 verbiage in order to adhere to AF doctrine language.

Note – highlighted text is the desired change to NHOP Chapter 5

Change sections below as highlighted (others are renumbered):

Previous Version:

5.5.1.1. Coordination. Any NOAA/NWS facility requesting aircraft reconnaissance (e.g., the NWS

Environmental Modeling Center (EMC), the Central Pacific Hurricane Center (CPHC)) should contact the

National Hurricane Center (NHC) no later than 1630 UTC the day prior to the requirement, and within the

constraints of paragraph 5.5.2.1. NHC will compile the list of the total DOC requirements for data on

tropical and subtropical cyclones or disturbances for the next 24-hour period (1100 to 1100 UTC) and an

outlook for the succeeding 24-hour period. This coordinated request will be provided to CARCAH as soon

as possible, but no later than 1630 UTC each day in the format of Figure 5-5.

5.5.3.1.1. CARCAH will coordinate the TCPOD with NHC, the 53 WRS, and NOAA AOC

before publication. 5.5.3.1.1.1. Combatant command headquarters and their air component

command headquarters will coordinate on missions by reviewing the proposed TCPOD posted at

http://www.nhc.noaa.gov/reconlist.shtml, then click ‘For Tomorrow’ under ‘Plan of the Day.’

5.5.3.1.1.2. Combatant command headquarters and their air component command

headquarters will pull current DOD missions from http://www.nhc.noaa.gov/reconlist.shtml,

34

Status:16Mar16

Recommendation

then click ‘For Today’ under ‘Plan of the Day.’ Additionally, the 403rd Current Operations

provides a mission setup sheet with reason of deviation from TCPOD, as required, to the

combatant command and their air component operations/command centers.

5.5.3.1.2. The TCPOD will list all DOC/NOAA AOC and DOD required tropical and subtropical cyclone

operational reconnaissance missions. Research missions will also be listed in the TCPOD when provided

to CARCAH before transmission time.

New Version:

5.5.1.1 Coordination. Any NOAA/NWS facility requesting aircraft reconnaissance (e.g., the

NWS Environmental Modeling Center (EMC), the Central Pacific Hurricane Center (CPHC)) should

contact the National Hurricane Center (NHC) no later than 1630 UTC the day prior to the requirement,

and within the constraints of paragraph 5.5.2.1. NHC will compile the list of the total DOC requirements

for data on tropical and subtropical cyclones or disturbances for the next 24-hour period (1100 to 1100

UTC) and an outlook for the succeeding 24-hour period. This coordinated request will be considered the

agency’s request for assistance (RFA) to DOD and will be provided to CARCAH as soon as possible, but

no later than 1630 UTC each day in the format of Figure 5-5.

5.5.3.1.1. CARCAH will coordinate the TCPOD with NHC, the 53rd WRS, and NOAA AOC

before publication.

5.5.3.1.1.1.1 The coordinated TCPOD is the agency’s RFA to DOD. Since DOD’s support

to NOAA is congressionally mandated and funded through the DOD Appropriations

Act, the coordinated TCPOD is considered a validated and approved RFA.

5.5.3.1.1.1.2 Combatant command headquarters and their air component command

headquarters will coordinate on missions by reviewing the proposed TCPOD posted at

http://www.nhc.noaa.gov/reconlist.shtml, then click ‘For Tomorrow’ under ‘Plan of the

Day.’

Congressionally mandated mission so RFA is approved as such. ADOPTED. CLOSED

UPON EDITING.

Para 2.3, bullet 3, remove “ as agreed to by DOD and DOC (see Appendix F)”

New Para 2.3 bullet 3: Meet DOC requirements for aircraft reconnaissance and other special observations.

Para 5.1 General. Delete this portion of sentence 2. As outlined in the Air Force Reserve Command

(AFRC)/National Oceanic and Atmospheric Administration (NOAA) Memorandum of Agreement (see

Appendix F).

New Para 5.1; General. All Department of Commerce (DOC) tropical and subtropical cyclone aircraft

reconnaissance needs will be requested and provided in accordance with the procedures of this

chapter. DOC has identified a requirement for, and the Department of Defense (DOD) maintains aircraft to

support, up to five sorties per day. Requirements exceeding five sorties will be accomplished on a

"resources-permitting" basis. In times of national emergency or war, some or all DOD

reconnaissance resources may not be available to fulfill DOC needs. The Global Decision Support

System (GDSS) JCS Priority Code for tasked, operational weather reconnaissance is 1A3 (IAW

DOD Regulation 4500.9-R and Joint Publications 4-01 and 4-04). The Force Activity Designator

(FAD)/Urgency of Need Designator (UND) Supply Priority Designator Determination code is

IIA2 (IAW Joint Publication 4-01 and Air Force Manual 23-110, Volume 2, Part 13, Attachment

3A-2.)

35

Status:6Apr16

Add para 5.2.1.3: Maintaining the capability of operating from two (2) deployed locations, as well as

from home station, simultaneously.

Remove NOAA/AFRC MOA from appendix F.

Ch 2.3 edited as above.

Ch 5.1 edited as above.

Ch 5.5.1.1 edited as above.

Ch 5.5.3.1.1.1.1 and 5.5.3.1.1.1.2 edited as above

Ch 5.5.3.1.12. Stays unchanged per submitters (2016/04/06)

Ch 5.2.1.3 added as recommended.