Parking Radius not large enough to accomodate AC

[aussiewannabe]

I’ve set up numerous FS9 Alaska airports to test my Alaskan Airlines traffic. In most cases, I can see either the 737-700 or -800 at Anchorage and final destinations.

However, there are some airports whose parking radius is not wide enough and preventing either the above AC to show.

Here are the airports:
Barrow PABR, current radius 82.20. Wing_span per aircraft.cfg – 94.75
Kotzebue PAOT, current radius 82.20. Wing_span per aircraft.cfg – 94.75
Adak PADK, current radius 82.20. Wing_span per aircraft.cfg – 94.75
Bethel PABE, airline assigned to parking spot is AKA (Korean Air) not ASA
Prudhoe Bay PASC, airline assigned to parking spot is AKA (Korean Air) not ASA

I’ve tried changing the radius and giving the parking spot an airline code (ASA), but the AFCAD (Lee Swordy) program wants to save it as an afcad2_ file.

Dillingham PADL also has an AKA spot, but the AC was placed in the larger parking spot with a radius of 101 feet.

What is the best way to fix this issue?

[aussiewannabe]

Update:

Barrow PABR Fixed. Changed radius to 96.00ft. Saved as afcad2_PABR.bgl
Prudhoe Bay PASC Fixed. Changed AKA to ASA. Saved as afcad2_PASC.bgl

Can't seem to fix Bethel PABE as it had the same issue as Prudhoe Bay. Since Dillingham PDAL is part of the flight plan, it'll just be to Dillingham all week.

Another plane flys to Kotzebue PAOT on Thursday and to Adak PADK Wednesday and Saturday. I'll just rewrite the flight plan to alternate between Barrow and Nome.

[arnoldmacdonald]

Increase parking radius to ~95–100 ft for the 737, and make sure both the AFCAD and aircraft.cfg use ASA for Alaska.
The afcad2_ filename is normal — just save it and place it in your scenery folder.
That should fix it basketball stars 2026

[aussiewannabe]

Increase parking radius to ~95–100 ft for the 737, and make sure both the AFCAD and aircraft.cfg use ASA for Alaska.
The afcad2_ filename is normal — just save it and place it in your scenery folder.
That should fix it basketball stars 2026

I just happen to stop in yesterday and found your reply.

Since posting this thread I found an AI Aircraft Radius Table and find it’s much easier to deal with AI in terms of metric rather than feet. Add to which, making sure the AI’s parking code is correct and given a parking spot with the afcad.

At one point I made a copy of my Traffic_AnchoragePANC.bgl file and started it over with some Cargo flights and moved on to other airports around the world.

Your reply had me return to dealing with parking at Bethel. I didn’t have to resize the parking radius as the 737 showed up where it was suppose to be. Although they don’t appear at Bethel at the same time, I resized a parking space to allow an Everts Air Cargo MD-83 to park elsewhere instead of in front of the Alaska Air Terminal. As it relates to Dillingham, no changing the radius was necessary. I’ve also redid the 737 flight plan to include Dillingham.

Later this week, I’ll check the 737 with flights to Nome, Barrow, Kotzebue and Adak.

One last thought: Adding flights that I have researched or tracked online over several years is fun, if not challenging. I get a great sense of satisfaction in seeing my FS2004 AI world come to life with these flights.