Winds aloft injection -- just an idea ...

[Hardy Heinlin]

Gary, remember the METAR method: PSX can generate a METAR text from the internal variables, and -- vice versa -- can read a pasted METAR text. And such situational PSX data is always in the network; the network can read internal variables as well as METAR texts.

I want to apply the same principle to aloft data. We'll have text. And we'll have internal variables. PSX can read text, and generate text. Of course, it also reads and writes it via the network to synchronize PSX instances. Add-ons can easily participate as usual.

So PSX has internal aloft data (self-made or injected) and, derived from that, PSX can generate a text in a big edit field. The generator provides a menu for various text formats (UPS, Cirrus, Lido, Asiana) by using neutral names:

- American
- British
- German
- Korean

Vice versa, when pasting a text, the menu is not needed as PSX detects the format automatically.

The user may edit the text in the edit field, and PSX will apply the edit in its internal variables. Same as with the METAR edit fields.

The existing jet stream model remains available. Everything's optional.


Regards,

|-|ardy

[Hardy Heinlin]

What FL does the TMP refer to if no FL is indicated?

Code Select Expand


IRRUS FLT PLAN
PAGE 7 OF 9 BA 9201/25 - PLAN  1 2232 25JUL18

LAT    LONG    WAYPT  ITT   DIS FL  TMP      SECTOR W/V

                                         100   200   310   350
N5128.7W00027.7 EGLL  269     4         
N5128.6W00031.0 D253B 151    10     P14 20019 19011 14016 12019
N5119.7W00023.1 D163J 136     1     M06 20018 18012 14015 12018
N5119.2W00022.3 EPM   091     4     M08 20018 18012 14015 12018
N5119.1W00015.1 DET32 091     3     M13 20018 18012 14015 12018
N5119.0W00010.4 D272H 091    24     M16 20018 18012 14015 12018
N5118.4E00027.9 D272E 091     5     M38 20018 18012 14015 12018


[cagarini]

The FLs are there HH... only don't matching the legend

100 200 310 350 ...

[Hardy Heinlin]

Those 4 FLs are for the winds.

See FL column between DIS and TMP columns.

The TMP has an extra FL as one single TMP cannot be applied to 4 different FLs.
Here the TMP in the last two lines refers to FL 350:

Code Select Expand

N4138.5W07232.8 HFD   058    37     M18 19066 23074 25093 24110
N4157.3W07150.6 PUT   041    16     M42 19060 23067 25094 24105
                                         310   330   350   370
N4520.4W06744.3 TOPPS 037   614 350 M54 26119 26127 25134 26141
N5259.9W05720.6 STEAM 057   100 350 M52 27093 27090 27084 27074

[cagarini]

Expected Alt / FL when crossing wp ?

[G-CIVA]

What FL does the TMP refer to if no FL is indicated?

The TMP refers to the expected ALT/FL reached overhead that WPT in the CLB/DES Phases.

Unfortunately it is one of the limitations of the CIRRUS output - it becomes rather vague in places.

This is where I personally believe Wind Data Outputs 1 & 2 have certain advantages in that WIND VECTOR, VELOCITY & TEMPERATURE data is recorded for each WPT at a selection of altitudes from below to above the CRZ ALT relevant to the RTE DATA> Page entry rules from TOC to T/D only.

[Hardy Heinlin]

Thank you.


On the Lido format, which gap size is correct?

This?

Code Select Expand

CLIMB T O C WKE30 YOROI
350 357/031 -40 330 338/027 -34 330 322/028 -34 330 322/028 -34


Or that?

Code Select Expand

CLIMB           T O C           WKE30           YOROI
350 357/031 -40 330 338/027 -34 330 322/028 -34 330 322/028 -34

[Bastien]

The first result you have was copied from the generated pdf flight plan
The second one is in a "pure" text format.

Code Select Expand

--------------------------------------------------------------------
                          WIND INFORMATION                         
                          ----------------                         

CLIMB            T O C            CEFOU            TUDEP
350 268/056 -49  370 267/062 -54  370 287/073 -54  370 220/071 -51
310 271/052 -39  350 262/056 -50  350 282/074 -50  350 217/080 -51
200 270/048 -14  330 260/051 -45  330 279/071 -46  330 218/080 -50
150 240/036 -08  310 261/047 -40  310 278/063 -41  310 222/070 -46
100 237/029 +03  290 263/044 -34  290 277/056 -36  290 228/059 -42

T O D            DESCENT
390 266/037 -49  350 250/056 -53
370 265/045 -50  310 250/059 -46
350 264/054 -51  200 259/039 -22
330 263/061 -50  150 270/025 -12
310 262/065 -47  100 296/012 -02


But in the same time, as the OFP is genereted automaticaly in PDF by Simbrief and, by the way, the Gary's Dispatch, you probably should accept both results, no ?

[Hardy Heinlin]

Should be no problem if waypoint identifiers have no spaces. But the "T O C" string may also represent three 1-letter NDB stations ...

How many words with spaces exist? Just "T O C" and "T O D"?

[Bastien]

Should be no problem if waypoint identifiers have no spaces. But the "T O C" string may also represent three 1-letter NDB stations ...

How many words with spaces exist? Just "T O C" and "T O D"?

As far as can see, it always begins by "CLIMB" followed by "T O C" and end by "T O D" followed by "DESCENT"

[simonijs]

Only just a little late to contribute..., but:

SimBrief also produces a PMDG Wind Uplink file (just like SimBrief produces an Aerowinx Route file). This file can be read by a Text editor and shows wind and temperature data for ten flight levels (although these levels are not mentioned).
However, these levels correspond to the Pressure Levels of 850 hPa, 700 hPa, 600 hPa, 500 hPa, 400 hPa, 300 hPa, 250 hPa, 200 hPa, 150 hPa and 100 hPa; and these Pressure Levels correspond to FL050, FL100, FL140, FL180, FL240, FL300, FL340, FL390, FL450 & FL530. Upper Wind Charts are published in accordance with these FL's, the vertical profile chart - produced by SimBrief - shows them all (except for FL530).

This provides a very nice vertical profile of the atmosphere, just like an atmospheric sounding does.

An example...:

HECA   265@14(18)   234@32(14)   232@36(   258@29(-5)   242@28(-12)
   222@33(-26)   210@31(-35)   190@33(-48)   176@36(-60)   173@37(-62)
CVO   265@14(18)   234@32(14)   232@36(   258@29(-5)   242@28(-12)
   222@33(-26)   210@31(-35)   190@33(-48)   176@36(-60)   173@37(-62)

Regards,
Simon

[Bastien]

Thanks Simon,
You're not late, I think Hardy is still collecting information that help to have a good overview to find standard/efficient solution design and data source.

[G-CIVA]

Simon & Bastien,

It looks like Hardy is reaching a very elegant solution for us - the only way I could see this data being incorporated is in its raw format i.e. copied as a body of text & pasted.

It could prove to be the solution from FL050 up to FL530. & it could negate all the variations of different Wind data outputs.

PFPX can create this file & the file be then saved to a folder/file structure wherever the user requires.  All one needs to do is then open it in .txt format & copy the data.

[Hardy Heinlin]

The UPS, Cirrus, Lido, and Asiana formats are sufficient now. Thanks, all.

Asiana has six wind records. That's my maximum for flight plan related purposes.


|-|ardy

[G-CIVA]

Hardy,

I have just had a rethink on my previous post, on closer inspection it could show promise but you seem to have finalised your plan in a certain direction now .... no worries.

On closer inspection my doubts about the .WX files are actually based around how 3rd party software interrogates the .WX file & draws data out of it & then inserts that into the RTE DATA> Page ... thats where issues begin.

Best

Steve

[G-CIVA]

Hardy,

As discussed in the Accessories Section.  PFPX produces UPS, AAR, CIRRUS (the same as SIMBRIEF) & this one:

Code Select Expand


WPT        FL320         FL340         FL360         FL380     
-----------------------------------------------------------------
NICHO    13019M48P00   13020M52P00   12017M52P05   11014M51P05   
NOSHO    06019M47P01   06019M51P01   05019M50P06   04020M49P07   
NANZA    01038M46P02   01036M50P02   01038M49P07   01040M48P09   
NOLTI    00052M45P04   00060M48P04   36061M48P08   36061M47P09   
NULUK    35046M42P06   35050M46P06   35049M48P09   34048M49P08   
NATES    30020M40P08   31025M45P08   31030M50P06   31035M55P01   
NIKLL    24025M39P10   25025M44P08   25026M50P06   26028M56P01   
NIPPI    29031M37P11   30034M42P10   31036M47P09   31038M51P05   
NOGAL    00020M34P14   01028M39P13   00028M45P12   00029M50P07   
NUBDA    05037M34P15   05042M39P14   05043M45P12   05044M50P07   
ALICE    04042M34P15   04045M38P14   04047M44P12   04049M49P07   
HPE      03040M33P15   03043M38P14   03046M44P12   03049M49P07   
GTC      03038M33P15   03040M38P14   03044M44P13   03047M49P08   
NESKO    03037M33P16   03036M38P15   03036M43P13   03036M49P08   
SAMON    04029M33P15   04027M38P14   04025M44P13   05023M49P08   
SAPRA    11013M34P15   11015M39P14   11016M44P12   11016M49P08   


Wind HDG & VELOCITY in KTS, TEMP in CELCIUS (M = minus P = plus), ISA Deviation (M = minus P = plus)

[simonijs]

PFPX can create this file & the file be then saved to a folder/file structure wherever the user requires.  All one needs to do is then open it in .txt format & copy the data.

Just one question, Steve: would I need PFPX for that (Windows based, I am on MAC)?

Simon

[Bastien]

Just one question, Steve: would I need PFPX for that (Windows based, I am on MAC)?

Simon

You're right actualy PFPX is windows compatible only. (payware + annual fees to download data such as Winds, METAR, TAF, Tracks and NOTAMs)

Simbrief/ Gary's PSX NET Dispatch are web based and free of charge (can donate)

I guess PFPX would be needed if the choice of using a unique "proprietary" format is done.
But Hardy seems to prudently choose some more "open" format as possible data source.

Regards
Bastien

[Hardy Heinlin]

Hardy,

As discussed in the Accessories Section.  PFPX produces UPS, AAR, CIRRUS (the same as SIMBRIEF) & this one:

Is this a preferred format among PSX users? I find that ISA deviation method cumbersome. Which 744 operator uses that?

Can we find the four most popular formats that PSX users prefer? At the moment I have:

UPS
Cirrus
Lido
Asiana

I'm not looking for the best one. I'm looking for the four most popular ones that are used by PSX users.

[Will]

Off topic: how often, during a real-world flight, are the forecast winds updated?

I confess, I've been loading the forecast winds into the FMC during preflight and then I don't think I ever update them after departure. The forecasts are generated every 6 hours, so the FMC could be updated once or twice during a long flight. Does that happen in real world operations?