December 1, 20232 yr LNM is flagging an airway altitude restriction based on the cruise altitude, when in fact the FP has valid altitudes for the altitude-restricted waypoints. I've seen a similar problem raised for a descent profile, but this seems to me to be somewhat different. FP copied below. Regards, Martin <?xml version="1.0" encoding="UTF-8"?> <LittleNavmap xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://www.littlenavmap.org/schema/lnmpln.xsd"> <Flightplan> <Header> <FlightplanType>IFR</FlightplanType> <CruisingAlt>36000</CruisingAlt> <CruisingAltF>36000.00000000</CruisingAltF> <CreationDate>2023-12-01T14:55:47+00:00</CreationDate> <FileVersion>1.2</FileVersion> <ProgramName>Little Navmap</ProgramName> <ProgramVersion>2.8.12</ProgramVersion> <Documentation>https://www.littlenavmap.org/lnmpln.html</Documentation> </Header> <SimData>MSFS</SimData> <NavData Cycle="2312">NAVIGRAPH</NavData> <AircraftPerformance> <FilePath>Boeing 787-10 MJC.lnmperf</FilePath> <Type>B78X</Type> <Name>Boeing 787-10 Dreamliner</Name> </AircraftPerformance> <Departure> <Pos Lon="-0.472198" Lat="51.472095" Alt="83.00"/> <Start>PARKING 573</Start> <Type>Parking</Type> <Heading>89.8828</Heading> </Departure> <Procedures> <SID> <Name>CPT5J</Name> <Runway>09R</Runway> </SID> <STAR> <Name>CABOT5</Name> <Runway>23</Runway> <Transition>CAYLY</Transition> </STAR> </Procedures> <Alternates> <Alternate> <Name>Greater Moncton Intl</Name> <Ident>CYQM</Ident> <Type>AIRPORT</Type> <Pos Lon="-64.678612" Lat="46.116112" Alt="477.00"/> </Alternate> </Alternates> <Waypoints> <Waypoint> <Name>Heathrow</Name> <Ident>EGLL</Ident> <Type>AIRPORT</Type> <Pos Lon="-0.461380" Lat="51.477501" Alt="83.00"/> </Waypoint> <Waypoint> <Name>Compton</Name> <Ident>CPT</Ident> <Region>EG</Region> <Type>VOR</Type> <Pos Lon="-1.219692" Lat="51.491573" Alt="6000.00"/> </Waypoint> <Waypoint> <Ident>DIDZA</Ident> <Region>EG</Region> <Airway>L9</Airway> <Type>WAYPOINT</Type> <Pos Lon="-1.395406" Lat="51.607697" Alt="9041.67"/> </Waypoint> <Waypoint> <Ident>OKSAW</Ident> <Region>EG</Region> <Airway>N14</Airway> <Type>WAYPOINT</Type> <Pos Lon="-1.685706" Lat="51.704254" Alt="12939.88"/> </Waypoint> <Waypoint> <Ident>BIBPE</Ident> <Region>EG</Region> <Airway>N14</Airway> <Type>WAYPOINT</Type> <Pos Lon="-1.852417" Lat="51.716362" Alt="14923.97"/> </Waypoint> <Waypoint> <Ident>OKTAD</Ident> <Region>EG</Region> <Airway>N14</Airway> <Type>WAYPOINT</Type> <Pos Lon="-2.546195" Lat="51.817909" Alt="23340.33"/> </Waypoint> <Waypoint> <Ident>MEDOG</Ident> <Region>EG</Region> <Type>WAYPOINT</Type> <Pos Lon="-3.549397" Lat="51.950367" Alt="35420.10"/> </Waypoint> <Waypoint> <Ident>VATRY</Ident> <Region>EI</Region> <Type>WAYPOINT</Type> <Pos Lon="-5.500000" Lat="52.554443" Alt="36000.00"/> </Waypoint> <Waypoint> <Ident>RIKUL</Ident> <Region>EI</Region> <Type>WAYPOINT</Type> <Pos Lon="-8.345778" Lat="53.057724" Alt="36000.00"/> </Waypoint> <Waypoint> <Ident>DOGAL</Ident> <Region>EI</Region> <Type>WAYPOINT</Type> <Pos Lon="-15.000000" Lat="54.000000" Alt="36000.00"/> </Waypoint> <Waypoint> <Ident>55N020W</Ident> <Type>USER</Type> <Pos Lon="-20.000000" Lat="55.000000" Alt="36000.00"/> </Waypoint> <Waypoint> <Ident>55N030W</Ident> <Type>USER</Type> <Pos Lon="-30.000000" Lat="55.000000" Alt="36000.00"/> </Waypoint> <Waypoint> <Ident>54N040W</Ident> <Type>USER</Type> <Pos Lon="-40.000000" Lat="54.000000" Alt="36000.00"/> </Waypoint> <Waypoint> <Ident>51N050W</Ident> <Type>USER</Type> <Pos Lon="-50.000000" Lat="51.000000" Alt="36000.00"/> </Waypoint> <Waypoint> <Ident>ALLRY</Ident> <Region>CY</Region> <Type>WAYPOINT</Type> <Pos Lon="-52.000000" Lat="50.500000" Alt="36000.00"/> </Waypoint> <Waypoint> <Name>Halifax Intl</Name> <Ident>CYHZ</Ident> <Type>AIRPORT</Type> <Pos Lon="-63.510193" Lat="44.879681" Alt="477.00"/> </Waypoint> </Waypoints> </Flightplan> </LittleNavmap>
December 1, 20232 yr Hi Martin, thanks for the flight plan. I see the issue but for now there is no solution except either ignoring these error messages or use direct in descent or climb. I'll have a look at it. Alex Alex' Projects: Little Navmap
December 1, 20232 yr Author Thanks Alex, I'm ignoring the messages as it doesn't seem to affect anything and LNM is happy to save a modified version of the plan with these issues. Martin
December 1, 20232 yr LNM does not drop any information if this kind of error occurs. This is only the case if you see messages like waypoint, SID, STAR or other not found. Alex Alex' Projects: Little Navmap
Archived
This topic is now archived and is closed to further replies.