CAPTAIN SIM FORUM - Problems with transatlantic flight

(UTC)


	Welcome, Guest. Please Login or Register

CAPTAIN SIM FORUM › 767 Captain (FSX) › 767 Captain (FSX) › Problems with transatlantic flight

‹ Previous Topic | Next Topic ›

Page Index Toggle

Pages: 1

Problems with transatlantic flight (Read 5606 times)

tyler767l Full Member Offline Posts: 9 Joined: Aug 12^th, 2013	Problems with transatlantic flight Aug 12^th, 2013 at 9:14pm	Print Post
	I am trying to do a flight from Washington-Dulles (KIAD) to Geneva (LSGG) but I am having problems with the flight plan on the FMS. On the display, it shows a waypoint called "LRP", but no matter how far I fly, or how much I zoom in or out, it is always directly in front of me. I cannot delete it from the FMS because it won't show it there. And when I try to add more waypoints, the path will try to go back to LRP. Does anyone have any ideas?


	IP Logged

Markoz CS Team Offline Posts: 12368 Location: Victoria, Australia Joined: Apr 24^th, 2009 Gender:	Re: Problems with transatlantic flight Reply #1 - Aug 13^th, 2013 at 6:50am	Print Post
	1. Which AIRAC are you using? 2. Where did you get you info for the Atlantic Tracks? Can you show us the entire route here so I (or anyone else who might want to) can test it out please.

	Mark Fletcher PC: i7 10700K @3.8/5.1GHz \| 64GB DDR4 3200 \| 12GB RTX 4070 Super \| 32" LCD Monitor \| 1TB SSD & 2x2TB SSD \| Win 11 Pro - FSX/FSX-SE/P3D3/P3D4/P3D5/P3D6/MSFS2020 15.6" Gaming Laptop: i7 7700HQ \| 32GB DDR4 \| 6GB GTX 1060 \| 256GB SSD & 1TB HDD \| Win 10 Pro 64bit - FSX-SE/P3D4
	IP Logged

tyler767l Full Member Offline Posts: 9 Joined: Aug 12^th, 2013	Re: Problems with transatlantic flight Reply #2 - Aug 13^th, 2013 at 9:50pm	Print Post
	Hi, I'm not sure what you mean by AIRAC, but I generated the route using FSBuild, and put it into the FMS by selecting the Flight Plan. But the route looked crazy with sharp turns, overlapping lines, and reverse. So I deleted all the legs and entered them in normally, but the leg called LRP won't remove itself, and I think it is causeing the problem. Here is the route in the .PLN file: Code <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> � �<Descr>AceXML Document</Descr> � �<FlightPlan.FlightPlan> � � � �<Title>KIAD to LSGG</Title> � � � �<FPType>IFR</FPType> � � � �<RouteType>HighAlt</RouteType> � � � �<CruisingAlt>35000</CruisingAlt> � � � �<DepartureID>KIAD</DepartureID> � � � �<DepartureLLA>N38� 56' 50.00",W77� 27' 35.00",+000000.00</DepartureLLA> � � � �<DestinationID>LSGG</DestinationID> � � � �<DestinationLLA>N46� 14' 17.00",E6� 6' 33.00",+000000.00</DestinationLLA> � � � �<Descr>KIAD, LSGG</Descr> � � � �<DeparturePosition>GATE D 23</DeparturePosition> � � � �<DepartureName>WASHINGTON_DULLES_INTL</DepartureName> � � � �<DestinationName>GENEVE</DestinationName> � � � �<AppVersion> � � � � � �<AppVersionMajor>10</AppVersionMajor> � � � � � �<AppVersionBuild>61472</AppVersionBuild> � � � �</AppVersion> � � � �<ATCWaypoint id="KIAD"> � � � � � �<ATCWaypointType>Airport</ATCWaypointType> � � � � � �<WorldPosition>N38� 56' 50.00",W77� 27' 35.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>KIAD</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="STOIC"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N39� 8' 58.00",W77� 40' 31.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>STOIC</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="DIXXE"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N39� 11' 59.00",W77� 40' 31.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>DIXXE</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="JEFFW"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N39� 14' 19.00",W77� 33' 33.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>JEFFW</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="COHEN"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N39� 15' 27.00",W77� 17' 36.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>COHEN</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="WOOLY"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N39� 20' 19.00",W77� 2' 11.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>WOOLY</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="LRP"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N40� 7' 11.00",W76� 17' 28.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>LRP</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="HOUTN"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N40� 20' 15.00",W75� 49' 38.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>HOUTN</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="KAYNE"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N40� 25' 27.00",W75� 38' 27.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>KAYNE</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="PARKE"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N40� 40' 59.00",W75� 4' 35.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>PARKE</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="BWZ"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N40� 47' 54.00",W74� 49' 18.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>BWZ</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="SAX"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N41� 4' 3.00",W74� 32' 17.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>SAX</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="FLOSI"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N41� 32' 36.00",W74� 20' 2.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>FLOSI</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="WEETS"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N41� 51' 27.00",W74� 11' 51.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>WEETS</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="ACOVE"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N42� 14' 5.00",W74� 1' 54.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>ACOVE</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="ALB"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N42� 44' 50.00",W73� 48' 11.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>ALB</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="RUMMY"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N43� 28' 41.00",W72� 10' 38.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>RUMMY</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="SQUAM"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N43� 46' 40.00",W71� 29' 0.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>SQUAM</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="FRIAR"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N44� 26' 28.00",W69� 53' 4.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>FRIAR</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="BGR"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N44� 50' 30.00",W68� 52' 26.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>BGR</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="YSJ"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N45� 24' 25.00",W65� 52' 15.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>YSJ</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="YYG"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N46� 17' 50.00",W63� 7' 10.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>YYG</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="UMETI"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N47� 34' 47.00",W59� 15' 29.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>UMETI</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="YQX"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N48� 53' 58.00",W54� 32' 5.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>YQX</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="5047N"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N50� 0' 0.00",W47� 0' 0.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>5047N</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="5139N"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N51� 0' 0.00",W39� 0' 0.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>5139N</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="5131N"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N51� 0' 0.00",W31� 0' 0.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>5131N</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="5123N"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N51� 0' 0.00",W23� 0' 0.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>5123N</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="5115N"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N51� 0' 0.00",W15� 0' 0.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>5115N</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="LESLU"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N51� 0' 0.00",W8� 0' 0.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>LESLU</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="INSUN"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N50� 23' 43.00",W6� 19' 23.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>INSUN</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="LND"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N50� 8' 10.00",W5� 38' 13.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>LND</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="DOLUR"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N49� 29' 4.00",W5� 3' 25.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>DOLUR</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="FIR01"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N49� 27' 21.00",W5� 1' 56.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>FIR01</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="GANTO"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N49� 23' 49.00",W4� 58' 51.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>GANTO</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="NERLA"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 59' 35.00",W4� 37' 55.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>NERLA</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="RUSIB"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 58' 37.00",W3� 48' 30.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>RUSIB</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="BETUV"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 57' 16.00",W3� 7' 19.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>BETUV</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="KOKOS"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 54' 25.00",W1� 40' 33.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>KOKOS</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="GALBO"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 50' 17.00",W0� 15' 0.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>GALBO</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="LGL"> � � � � � �<ATCWaypointType>VOR</ATCWaypointType> � � � � � �<WorldPosition>N48� 47' 26.00",E0� 31' 49.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>LGL</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="DITAL"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 44' 40.00",E0� 53' 21.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>DITAL</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="PIGOP"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 41' 8.00",E1� 20' 20.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>PIGOP</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="TABOV"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 38' 39.00",E1� 38' 56.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>TABOV</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="RESMI"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 34' 6.00",E2� 11' 30.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>RESMI</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="ODEBU"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 16' 51.00",E2� 37' 34.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>ODEBU</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="OGULO"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N48� 13' 5.00",E2� 40' 9.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>OGULO</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="LUSAR"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N46� 40' 8.00",E5� 10' 45.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>LUSAR</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="SAUNI"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N46� 37' 24.00",E5� 28' 40.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>SAUNI</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="LIRKO"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N46� 34' 14.00",E5� 48' 51.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>LIRKO</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="DINIG"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N46� 29' 43.00",E5� 53' 26.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>DINIG</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="SOVAD"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N46� 20' 14.00",E6� 2' 53.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>SOVAD</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="GG507"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N46� 26' 27.00",E6� 11' 59.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>GG507</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="GG514"> � � � � � �<ATCWaypointType>Intersection</ATCWaypointType> � � � � � �<WorldPosition>N46� 32' 25.00",E6� 20' 49.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>GG514</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � � � �<ATCWaypoint id="LSGG"> � � � � � �<ATCWaypointType>Airport</ATCWaypointType> � � � � � �<WorldPosition>N46� 14' 17.00",E6� 6' 33.00",+000000.00</WorldPosition> � � � � � �<ICAO> � � � � � � � �<ICAOIdent>LSGG</ICAOIdent> � � � � � �</ICAO> � � � �</ATCWaypoint> � �</FlightPlan.FlightPlan> </SimBase.Document>


	IP Logged

Markoz CS Team Offline Posts: 12368 Location: Victoria, Australia Joined: Apr 24^th, 2009 Gender:	Re: Problems with transatlantic flight Reply #3 - Aug 14^th, 2013 at 2:50am	Print Post
	That's not quite what I meant, but it will do. I'll use that to create a new PLN file (or just use the waypoints within it if necessary) and then give it a test. I create flights using FSC 9 (now at version 9.3). It makes it easier with figuring out which SID's, Jet Airways, STAR's and Transitions to use for the flight I plan to do. It can also download the latest North Atlantic Tracks for use in the flight plan. This is why I asked where you got the Atlantic Tracks (I forgot to write North Atlantic Tracks in my previous reply) info from.

	Mark Fletcher PC: i7 10700K @3.8/5.1GHz \| 64GB DDR4 3200 \| 12GB RTX 4070 Super \| 32" LCD Monitor \| 1TB SSD & 2x2TB SSD \| Win 11 Pro - FSX/FSX-SE/P3D3/P3D4/P3D5/P3D6/MSFS2020 15.6" Gaming Laptop: i7 7700HQ \| 32GB DDR4 \| 6GB GTX 1060 \| 256GB SSD & 1TB HDD \| Win 10 Pro 64bit - FSX-SE/P3D4
	IP Logged

Markoz CS Team Offline Posts: 12368 Location: Victoria, Australia Joined: Apr 24^th, 2009 Gender:	Re: Problems with transatlantic flight Reply #4 - Aug 14^th, 2013 at 1:25pm	Print Post
	Okay. I've done your flight. It went fine. BUT.... 1. After pasting the route into notepad and saving it as a PLN, I could not open it in FSX. Every time it "loaded", the flight plan remained as nothing. 2. I can't find the first 3 waypoints! STOIC, DIXXE or JEFFW. Nor could I find the waypoints KAYNE and INSUN. I can't find them in FSC9, FS Map or FS Flight Planner. Not even at the LON/LAT co-ordinates in the PLN you gave. So how did you create the flight plan? Did you use the default FS Flight Planner? 3. The LRP waypoint was not a problem for me at all. Once I reached it, the 767 continued on to the next waypoint and I never saw LRP again over the next 8 or so hours of the flight. I have no idea why it stayed in front of you all the time or why you couldn't delete it. So this one is a mystery to me.

	Mark Fletcher PC: i7 10700K @3.8/5.1GHz \| 64GB DDR4 3200 \| 12GB RTX 4070 Super \| 32" LCD Monitor \| 1TB SSD & 2x2TB SSD \| Win 11 Pro - FSX/FSX-SE/P3D3/P3D4/P3D5/P3D6/MSFS2020 15.6" Gaming Laptop: i7 7700HQ \| 32GB DDR4 \| 6GB GTX 1060 \| 256GB SSD & 1TB HDD \| Win 10 Pro 64bit - FSX-SE/P3D4
	IP Logged

tyler767l Full Member Offline Posts: 9 Joined: Aug 12^th, 2013	Re: Problems with transatlantic flight Reply #5 - Aug 14^th, 2013 at 11:09pm	Print Post
	Hi, Quote: 1. After pasting the route into notepad and saving it as a PLN, I could not open it in FSX. Every time it "loaded", the flight plan remained as nothing. Not sure why this happened. It worked fine for me. Quote: 2. I can't find the first 3 waypoints! STOIC, DIXXE or JEFFW. Nor could I find the waypoints KAYNE and INSUN. I can't find them in FSC9, FS Map or FS Flight Planner. Not even at the LON/LAT co-ordinates in the PLN you gave. So how did you create the flight plan? Did you use the default FS Flight Planner? After you load the flight plan, did you click "find route?" when you do that, FS completely ignores the route you just loaded and makes its own. Quote: 3. The LRP waypoint was not a problem for me at all. Once I reached it, the 767 continued on to the next waypoint and I never saw LRP again over the next 8 or so hours of the flight. I have no idea why it stayed in front of you all the time or why you couldn't delete it. So this one is a mystery to me. Me too. But today when I loaded the saved flight, it was still there, but somewhere in the remaining flight, LRP disappeared. � But I was able to finish the flight without any problems. Thanks


	IP Logged

Markoz CS Team Offline Posts: 12368 Location: Victoria, Australia Joined: Apr 24^th, 2009 Gender:	Re: Problems with transatlantic flight Reply #6 - Aug 15^th, 2013 at 2:53am	Print Post
	Quote: Quote: 1. After pasting the route into notepad and saving it as a PLN, I could not open it in FSX. Every time it "loaded", the flight plan remained as nothing. Not sure why this happened. It worked fine for me. Me either! Quote: Quote: 2. I can't find the first 3 waypoints! STOIC, DIXXE or JEFFW. Nor could I find the waypoints KAYNE and INSUN. I can't find them in FSC9, FS Map or FS Flight Planner. Not even at the LON/LAT co-ordinates in the PLN you gave. So how did you create the flight plan? Did you use the default FS Flight Planner? After you load the flight plan, did you click "find route?" when you do that, FS completely ignores the route you just loaded and makes its own. I couldn't select "find route", the button was greyed out. That's because the flight plan did not load. After selecting the plan and pressing OPEN to load it, the FS Flight Planner page simply remained BLANK (no departure airport listed, no arrival airport list and therefore no route between them). In the end, I created the route using the waypoints as listed in the PLN that I copied from your post. Interestingly enough, the location of KIAD is different in mine: <DepartureID>KIAD</DepartureID> �<DepartureLLA>N38� 56' 22.51",W77� 27' 35.18",+000312.00</DepartureLLA> This is from yours: <DepartureID>KIAD</DepartureID> �<DepartureLLA>N38� 56' 50.00",W77� 27' 35.00",+000000.00</DepartureLLA> The same applies to quite a lot of the waypoints in the route. I curious to find out why they are different. I mean we both ARE using FSX aren't we? Quote: Quote: 3. The LRP waypoint was not a problem for me at all. Once I reached it, the 767 continued on to the next waypoint and I never saw LRP again over the next 8 or so hours of the flight. I have no idea why it stayed in front of you all the time or why you couldn't delete it. So this one is a mystery to me. Me too. But today when I loaded the saved flight, it was still there, but somewhere in the remaining flight, LRP disappeared. � But I was able to finish the flight without any problems. Definitely a mystery! Anyway, I'm glad you were able to complete the route without problems in the end.

	Mark Fletcher PC: i7 10700K @3.8/5.1GHz \| 64GB DDR4 3200 \| 12GB RTX 4070 Super \| 32" LCD Monitor \| 1TB SSD & 2x2TB SSD \| Win 11 Pro - FSX/FSX-SE/P3D3/P3D4/P3D5/P3D6/MSFS2020 15.6" Gaming Laptop: i7 7700HQ \| 32GB DDR4 \| 6GB GTX 1060 \| 256GB SSD & 1TB HDD \| Win 10 Pro 64bit - FSX-SE/P3D4
	IP Logged

LOU Beta Team Offline 727,707,747,757,767= 40years of Boeings Posts: 1593 Location: Central PA, USA Joined: Mar 3^rd, 2010 Gender:	Re: Problems with transatlantic flight Reply #7 - Aug 15^th, 2013 at 6:04pm	Print Post
	I thought I would try this flight too, since I flew it many times in real life in a 767-200. I did not include page 7 as it was just the hold after a missed approach. I don't have any current charts, so I just looked on line at Europe high level maps and made up my own route. Just my 2 cents. Lou Uploaded with ImageShack.us

	Processor: Intel Core i7-4770k @3.5Ghz Memory: 6Gb DDR3 1600mhz Video: NVIDIA GeForce GTX 680 Storage: 256Gb Samsung 840 Pro \| 120Gb OCZ Agility 3 \| WD Black 640Gb 7200rpm 55" Samsung LED - HDTV for monitor
	IP Logged

Markoz CS Team Offline Posts: 12368 Location: Victoria, Australia Joined: Apr 24^th, 2009 Gender:	Re: Problems with transatlantic flight Reply #8 - Aug 16^th, 2013 at 6:18am	Print Post
	I use FSC9, with RouteFinder (free) to get the route with the Jetways provided, then I create the route in the CDU/FMC and add a SID, STAR and ARRIVAL RWY. I do not usually make them with the FS Flight Planner, although I have sometimes saved the FSC9 flight plan as a PLN (in the Documents/Flight Simulator X files folder) and then loaded it into the CDU/FMC, then add the SID, STAR and ARRIVAL RWY to that route and it works fine. I desperately want to know where those waypoints that I couldn't find in the FS Flight Planner, or FSC9, came from. I'm very curious for the answer to that question. HINT HINT

	Mark Fletcher PC: i7 10700K @3.8/5.1GHz \| 64GB DDR4 3200 \| 12GB RTX 4070 Super \| 32" LCD Monitor \| 1TB SSD & 2x2TB SSD \| Win 11 Pro - FSX/FSX-SE/P3D3/P3D4/P3D5/P3D6/MSFS2020 15.6" Gaming Laptop: i7 7700HQ \| 32GB DDR4 \| 6GB GTX 1060 \| 256GB SSD & 1TB HDD \| Win 10 Pro 64bit - FSX-SE/P3D4
	IP Logged

Page Index Toggle

Pages: 1

‹ Previous Topic | Next Topic ›

« Board Index ‹ Board ^Top

CAPTAIN SIM FORUM » Powered by YaBB 2.6.0!
YaBB Forum Software © 2000-2024. All Rights Reserved.

Valid XHTML

Valid CSS

Powered by Perl

Source Forge