Search the Community
Showing results for tags 'close'.
Found 1 result
Hi I've created a custom schedule and from testing it I am getting a lot of "=> ***** close cross incoming range" errors in regards to arrival aircraft. I did some initial research and found this topic but there is no set solution. I know this issue is to do with arrivals only. And that it is related to crossing runways - I personally am unsure how the sim calculates how an arrival is granted permission to spawn. I have uploaded the log file and uploaded a spreadsheet to help better understand what could be the issue here. Situation: Airport: KLAS Runway Setup: - 26L active (all arrivals) - 26R departures (commercial mainly - 1z Janet and 1z GA departure) - 19L departures (GA only) - 19R arrivals for GA that are transferred from 26L NOTE: I cannot make 19L an active as I require commercial aircraft only on 26L, which we cannot implement currently in schedules. If we activate 19L as well, then commercial aircraft will spawn on this runway which is something I want to avoid completely. All arrival aircraft spawn on time, up until SWA6885. This arrival is NOT the first one with the error messages "=> ***** close cross incoming range" but it is the first one that is considerably late. Onwards from here, 72% of arrivals from this point are delayed considerably. DAL2832 is the first aircraft to get the error message, followed by (in the order shown): DAL2832 - scheduled at 12:27 to land around 12:34 (spreadsheet contains this data) - between DAL2832 and SWA6885, there are x4 arrivals that spawn with no such error message SWA6885 SWA6448 WWI93 (GA) ASA1410 SWA3552 SWA541 AAL2456 N18ZD (GA) DAL1097 SWA378 UAL462 RSP137 (GA) What is happening (time stamp wise): @ 12:27, DAL2832 [arr] spawns on app to 26L > Lands @ 12:34:58 (on time) --- Between 12:28 and 12:37 all arrivals spawn on time & all departures spawn on time (i.e. pushback) @ 12:33:01, N93124 (GA) lines up on 19L & immediately starts her takeoff roll @ 12:34:07 JSX108 (GA) lines up on 19L & immediately starts her takeoff roll @ 12:34:55 JSX108 (GA) has taken off successfully @ 12:35:25 PWA454 (GA) spawns on app to 26L > Lands @ 12:46:55 (on time) @ 12:35:59 PWA454 (GA) begins her turn onto final approach for 19R @ 12:37:00 SWA5742 (arrival prior to SWA6885) spawns on time on to 26L > Lands @ 12:43:58 (on time) @ 12:38:00 SWA6885 attempts to spawn for the first time (denied with error "***** close cross incoming range") --- There are x4 attempts between now and 12:38:36 with the same error for SWA6885 @ 12:38:36 SWA6885 attempts again to spawn onto 26L - Even though there is more than 5nm seperation now to SWA5742 - There is also no GA landing on 19R or departing 19L - However PWA454 is on app to 19R - not sure how far out (I will assume 46 mins - 38 mins = 8 mins - So probably about to turn onto finals [basing upon the 7 min approach]) --- @ 12:41:19, I believe PWA454 turns onto finals for 19R as log state changes from "FINALRUNWAY" to "STATE_INCOMING" @ 12:38:51 LXJ528 (GA) lines up on 19R & immediately starts her takeoff roll --- SWA6885 is continuing to try to spawn @ 12:39:55 LXJ528 (GA) has taken off successfully @ 12:40:00 Now SWA6448 tries to spawn on time without success and the same error message -- PWA454 on 19R app. is now (00:46:55 - 00:40:00 = 7 mins odd) therefore about 13-15nm out from 19R -- SWA5742 on 26L app. is now (12:43:58 - 00:40:00 = 4 mins odd) therefore about 6/7nm out from 26L And so forth ... Why aren't these arrivals spawning when there is plenty of separation? It cannot be due to crossing runways because 26L and 19R or 19L do NOT cross according to the ADIRS radar. FORUM.xlsx 1st_attempt_log.txt