I always fly IFR with the default FSX ATC, with flightplans created by FSBuild. I'm not too crazy about the built in ATC, but I use this function to communicate with the tower to get into the takeoff queue for permission for taxi/takeoff, and for landing. Lately, I have found that almost every flight plan I import into the FSX flight planner to obtain ATC supervision is not accepted, and as a result I have to fly VFR. I can live with this, since I can still get departure and landing coverage from the tower, but in real IFR conditions I will be denied flight following. That means when I can't get IFR clearance at startup, and subsequently when I ask for taxi instructions it will say the weather is IFR, request denied. I can create a flightplan with the FSX flight planner but it doesn't choose a realistic routing.I don't know why this is happening, could it be that there are waypoints in the flightplans that are not recognized by FSX? My PMDG heavies recognize the newer RNAV waypoints and such since they are included in the latest navdata updates, but I wonder if FSX won't because its not in the default FSX database, and as a result the program is confused and will not accept flightplans with these unrecognized waypoints. I can just ignore this and taxi and fly as I please, but then ATC won't see me in the takeoff queues and other a/c will taxi through me to the runway, which ruins the realism factor. But the good news is this only happens when the weather is bad enough to be IFR.Hope this makes sense.

The nav database for FSX is fixed and can not be updated, anyway no one has ever taken the time to hack FSX so it can be updated.So FSX will not recognize any new or modified waypoints that are post 2005-2006, what ever the cutoff date was.You can test this by taking one of the flight plans that will not load and start deleting the waypoints one by one. I do not use FSBuild so I do not know what they look like, but if it is saved as a standard FSX pln then it would look like this.[flightplan]title=KNZY to KNIPdescription=KNZY, KNIPtype = IFRroutetype = 3cruising_altitude=0departure_id=KNZY, N32* 41.95', W117* 12.92', +000026.00destination_id=KNIP, N30* 14.15', W81* 40.83', +000022.00departure_name=North_Island_NAS_/_Halsey_Fielddestination_name=Jacksonville_NASwaypoint.0=KNZY, A, N32* 41.95', W117* 12.92', +000000.00, waypoint.1=IPL, V, N32* 44.93', W115* 30.51', +000000.00, waypoint.2=CLL, V, N30* 36.30', W096* 25.24', +000000.00, waypoint.3=TAY, V, N30* 30.28', W082* 33.17', +000000.00, waypoint.4=KNIP, A, N30* 14.15', W081* 40.83', +000000.00,Next open in Notepad or something similar, just delete a waypoint, renumber the waypoints like below, save under a different pln name and try it.[flightplan]title=KNZY to KNIPdescription=KNZY, KNIPtype = IFRroutetype = 3cruising_altitude=0departure_id=KNZY, N32* 41.95', W117* 12.92', +000026.00destination_id=KNIP, N30* 14.15', W81* 40.83', +000022.00departure_name=North_Island_NAS_/_Halsey_Fielddestination_name=Jacksonville_NASwaypoint.0=KNZY, A, N32* 41.95', W117* 12.92', +000000.00, waypoint.1=IPL, V, N32* 44.93', W115* 30.51', +000000.00, waypoint.2=TAY, V, N30* 30.28', W082* 33.17', +000000.00, waypoint.3=KNIP, A, N30* 14.15', W081* 40.83', +000000.00,

Actually, there is a very handy utility that will update the FSX database. I've used it myself and can now fly SIDs and STARs that have waypoints/fixes that weren't in the original FSX databse. Here's the link - might be worth checking it out, as it could well solve your problem of FSX rejecting your flight plans..http://www.btinternet.com/~gb.mitch/index.htmlRegardsBrian Wilks

Shouldn't this thread have been titled FSbuild won't produce FSX IFR flight plan?

Shouldn't this thread have been titled FSbuild won't produce FSX IFR flight plan?

FSbuild does produce IFR flight plans - I use it myself.With respect to the O.P. I have used FSbuild to produce all of my flight plans, these utilise sids and stars when necessary. When building the flight plan, ensure that the export to FSX option is checked (which i presume you have done since you are getting as far as loading the flightplan in to fsx).My comments dont provide a solution, but do confirm that FSbuild using sids, stars and other waypoints/intersections etc does work and has no effect on my add on planes.Tom

Actually, there is a very handy utility that will update the FSX database. I've used it myself and can now fly SIDs and STARs that have waypoints/fixes that weren't in the original FSX databse. Here's the link - might be worth checking it out, as it could well solve your problem of FSX rejecting your flight plans..http://www.btinternet.com/~gb.mitch/index.htmlRegardsBrian Wilks

Brian,A while back I downloaded the most recent AIRAC update available and replaced the default FSX database with it. It does add a lot of intersections that weren't in the default ATC database. But one negative is that many of the Victor and Jet routes are "incomplete". That is, the routes are "partial" and so it makes it somewhat more difficult to find your waypoints if they are on a specific V-Route or J-Route, as opposed to the default database which shows the entire route. Don't know why this is.

Actually, there is a very handy utility that will update the FSX database. I've used it myself and can now fly SIDs and STARs that have waypoints/fixes that weren't in the original FSX databse. Here's the link - might be worth checking it out, as it could well solve your problem of FSX rejecting your flight plans..http://www.btinternet.com/~gb.mitch/index.htmlRegardsBrian Wilks

Learn something all the time!

I don't know why this is happening, could it be that there are waypoints in the flightplans that are not recognized by FSX?

I don't think FSX ATC cares what waypoints are in the plan. I had no problems getting an IFR clearance for either of these plans. The waypoints were just set randomly with made up names (FSX format/FS9 format):

<?xml version="1.0" encoding="UTF-8"?><SimBase.Document Type="AceXML" version="1,0">    <Descr>AceXML Document</Descr>    <FlightPlan.FlightPlan>        <Title>KNZY to KNIP</Title>        <FPType>IFR</FPType>        <CruisingAlt>13000</CruisingAlt>        <DepartureID>KNZY</DepartureID>        <DepartureLLA>N32° 42' 1.42",W117° 12' 25.69",+000026.00</DepartureLLA>        <DestinationID>KNIP</DestinationID>        <DestinationLLA>N30° 13' 47.99",W81° 39' 51.10",+000022.00</DestinationLLA>        <Descr>KNZY, KNIP</Descr>        <DeparturePosition>PARKING 1</DeparturePosition>        <DepartureName>North Island NAS</DepartureName>        <DestinationName>Jacksonville NAS</DestinationName>        <AppVersion>            <AppVersionMajor>10</AppVersionMajor>            <AppVersionBuild>61472</AppVersionBuild>        </AppVersion>        <ATCWaypoint id="KNZY">            <ATCWaypointType>Airport</ATCWaypointType>            <WorldPosition>N32° 42' 1.42",W117° 12' 25.69",+000026.00</WorldPosition>            <ICAO>                <ICAOIdent>KNZY</ICAOIdent>            </ICAO>        </ATCWaypoint>        <ATCWaypoint id="BAD01">            <ATCWaypointType>User</ATCWaypointType>            <WorldPosition>N34° 11' 55.95",W111° 38' 17.20",+013000.00</WorldPosition>        </ATCWaypoint>        <ATCWaypoint id="BAD02">            <ATCWaypointType>User</ATCWaypointType>            <WorldPosition>N31° 56' 7.16",W102° 26' 55.01",+013000.00</WorldPosition>        </ATCWaypoint>        <ATCWaypoint id="BAD03">            <ATCWaypointType>User</ATCWaypointType>            <WorldPosition>N33° 44' 46.19",W93° 24' 35.16",+013000.00</WorldPosition>        </ATCWaypoint>        <ATCWaypoint id="BAD04">            <ATCWaypointType>User</ATCWaypointType>            <WorldPosition>N31° 1' 47.64",W88° 8' 13.57",+013000.00</WorldPosition>        </ATCWaypoint>        <ATCWaypoint id="KNIP">            <ATCWaypointType>Airport</ATCWaypointType>            <WorldPosition>N30° 13' 47.99",W81° 39' 51.10",+000022.00</WorldPosition>            <ICAO>                <ICAOIdent>KNIP</ICAOIdent>            </ICAO>        </ATCWaypoint>    </FlightPlan.FlightPlan></SimBase.Document>

[flightplan]title=KNZY to KNIPdescription=KNZY, KNIPtype=IFRroutetype=3cruising_altitude=13000departure_id=KNZY,N32* 41.56', W117* 12.54',+000023.00departure_position=11destination_id=KNIP,N30* 14.05', W081* 40.35',+000020.00departure_name=NORTH_ISLAND_NAS destination_name=JACKSONVILLE_NAS alternate_name=JACKSONVILLE_NAS waypoint.0=KNZY, A, N32* 41.56', W117* 12.54',+000023,waypoint.1=BAD01, N, N34° 11' 55.95" , W111° 38' 17.20" , +013000.00, waypoint.2=BAD02, N, N31° 56' 7.16" , W102° 26' 55.01" , +013000.00, waypoint.3=BAD03, N, N33° 44' 46.19" , W93° 24' 35.16" , +013000.00, waypoint.4=BAD04, N, N31° 1' 47.64" , W88° 8' 13.57" , +013000.00, waypoint.5=KNIP, A, N30* 14.05', W081* 40.35',+000020,

Waypoints and navaids can be added to FSX, but moving default ones is problematic. There is no exclusion mechanism for default waypoints and navaids. so the only option is to update the default ATX and NVX files. I know someone is doing that for Alaska.I have seen some update files available for download, and among other things they don't include the airway data (V route / J route) so they might break the default flight planner. Also, for enroute VORs which typically are part of airways, there is a collocated waypoint to hold the airway data. So when you move the VOR you need to move the waypoint.scott s..

In case anyone is curious, I found the culprit in my FS flight plan (produced by FSBuild) that prevented it from being recognized by FSX ATC. Because it was an oceanic crossing using Nat track coordinates, I had 4 entries of lat long coordinates over the ocean: BIBT1G UZ28 SUPUR UL602 NALAX UL46 MITSO UL46 REMSI UP6 MASOP UP6 NELBO UN551 NIBOG PIKIL 5700N/02000W 5800N/03000W 5800N/04000W 5700N/05000W LOACH FOXXE N264A TAFFY SCUPPThe bold entries are the errant coordinates that the FSX ATC was choking on. I suspected that those 4 "waypoints" may be the problem, so I deleted those waypoints and rebuilt the flight plan in FSBuild for export to FSX. As it turns out, the revised flight plan without those waypoints is now accepted by FSX, and I can get proper IFR clearance. This seems strange to me, because I have done plenty of oceanic crossings last year and the FSX ATC still gave me IFR clearance even thought the FSBuild flightplan had the lat/long coordinates in them. Not sure why this is a recent issue for me, but it does seem that any flight I attempted recently using these kinds of waypoints would result in me not being able to obtain IFR from ATC. I wonder if there is a proper syntax I can enter for these coordinates to get FSX ATC to recognize them. In the meantime, I'm going to produce one flightplan without the problem coordinates for the FSX flightplanner to recognize, and a separate "proper" fsbuild flightplan with the oceanic coordinates to use in the aircraft FMC.

One last note of interest....I had replied that the lat/long coordinates over the ocean were the problem. Actually, the syntax of those coordinates was incorrect and not accepted by the FSX flight planner/ATC. FSBuild and the addon FMC's it exports flightplans to can accept a variety of syntax for these waypoints, but FSX cannot recognize all the different syntax. I recreated the flight plan with a different format, and I was able to read the exported FSX formatted flightplan successfully.Original Plan (PMDG FMC reads it but not FSX)BIBT1G UZ28 SUPUR UL602 NALAX UL46 MITSO UL46 REMSI UP6 MASOP UP6 NELBO UN551 NIBOG PIKIL 5700N/02000W 5800N/03000W 5800N/04000W 5700N/05000W LOACH FOXXE N264A TAFFY SCUPPCorrected Plan:BIBT1G UZ28 SUPUR UL602 NALAX UL46 MITSO UL46 REMSI UP6 MASOP UP6 NELBO UN551 NIBOG PIKIL 57/20 58/30 58/40 57/50 LOACH FOXXE N264A TAFFY SCUPPIn case anyone runs into this situation, use the xx/xx format for ocean crossing lat long points and you should be fine!

Actually, there is a very handy utility that will update the FSX database. I've used it myself and can now fly SIDs and STARs that have waypoints/fixes that weren't in the original FSX databse. Here's the link - might be worth checking it out, as it could well solve your problem of FSX rejecting your flight plans..http://www.btinterne...itch/index.htmlRegardsBrian Wilks

Does work for FSX? I only saw FS9.

Brian,A while back I downloaded the most recent AIRAC update available and replaced the default FSX database with it. It does add a lot of intersections that weren't in the default ATC database. But one negative is that many of the Victor and Jet routes are "incomplete". That is, the routes are "partial" and so it makes it somewhat more difficult to find your waypoints if they are on a specific V-Route or J-Route, as opposed to the default database which shows the entire route. Don't know why this is.

I think this is because the fixes were updated, but not the airways. I had a similar problem in FS9.

Yes, it works perfectly OK with FSX (which is the system I use). It's mentioned in the FAQ's (although admittedly it's tucked away somewhat).CheersBrian

...This seems strange to me, because I have done plenty of oceanic crossings last year and the FSX ATC still gave me IFR clearance even thought the FSBuild flightplan had the lat/long coordinates in them.....

Slightly OT: How does the default ATC deal with oceanic procedures? Do you have to call in for clearance, then post position reports etc like in real life, or does it pretend that it has radar coverage over the ocean as well and that the procedures are no different than when flying anywhere else?

Slightly OT: How does the default ATC deal with oceanic procedures? Do you have to call in for clearance, then post position reports etc like in real life, or does it pretend that it has radar coverage over the ocean as well and that the procedures are no different than when flying anywhere else?

In FSX the ATC has always radar coverage.

Slightly OT: How does the default ATC deal with oceanic procedures? Do you have to call in for clearance, then post position reports etc like in real life, or does it pretend that it has radar coverage over the ocean as well and that the procedures are no different than when flying anywhere else?

It treats the ocean crossings like land crossings, radar is always on. However, you will be following the the proper facilities (i.e., Gander over the border of Canada to Shanwick Center in Ireland). You will have to pretend to do ETOPS or proper NAT Track procedures.