Jump to content

KJFK problem


Recommended Posts

Noticed this to lately. You have to direct those to their end point with a DIRECT command.

And often you can't do this with mouse because that end point does not appear on the screen! It is only after you type the D command that the fix appears.

These are aircraft that do not depart via a SID. I suppose that is normal to have some departing without using the SID? Yes, the SID option is ticked.

Link to comment
Share on other sites

And often you can't do this with mouse because that end point does not appear on the screen! It is only after you type the D command that the fix appears.

These are aircraft that do not depart via a SID. I suppose that is normal to have some departing without using the SID? Yes, the SID option is ticked.

You can enable the navigation points if you want. Are you using navdata files or the default database? I use the latest navdata files and I don't have this issue at JFK right now.

Link to comment
Share on other sites

You can enable the navigation points if you want. Are you using navdata files or the default database? I use the latest navdata files and I don't have this issue at JFK right now.

I am using the default, but that end fix must be in there because it pops up as soon as I enter the DIRECT command?

Enabling navigation points will light up the nav-aids like VOR and NDB but not the "fixes".

Edit: I need to clarify this, now that I have investigated further. I have found this particular FIX will show up on the screen if I tick ALL (resulting in a somewhat cluttered screen) but if I tick only the SIDs for the active departure runway, that FIX does not appear. Further testing shows this FIX is included in a SID for another runway! But aircraft departing from the active runway can still plan to depart via this "hidden" FIX. In that case, the only way to get the aircraft to that FIX is to use the DIRECT command, specifying the name of that FIX. I think this is a bug and the FIX should be displayed so the mouse can be used.

Maybe when Robert implements the enhancement to display the full planned track for the selected aircraft, this problem will disappear.

Link to comment
Share on other sites

This is a nice one for Robert: When generating departures, are the all SIDs considered or only those for the departing runway? The post above by tumbi suggests a departing plane is assigned to a sid not available for that runway.

Link to comment
Share on other sites

This is a nice one for Robert: When generating departures, are the all SIDs considered or only those for the departing runway? The post above by tumbi suggests a departing plane is assigned to a sid not available for that runway.

No, it is not departing on a SID. I find lots of departures leave without using a SID. Maybe half do and half don't. Those that don't simply plan to go direct to one of the fixes, maintaining runway heading until told otherwise.
Link to comment
Share on other sites

I have another problem with the 3 airports in NY.

For KJFK rwy 04L and 04R, KLGA rwy 04 and KEWR rwy 04L and 04R are not oriented well.

For KJFK their position is 030 where irl the position is 045, same goes for LGA and EWR with the runways about 15 degrees out of position.

Now a problem arise when playing jfk with 04L departing and 04R arrivals. since the aircrafts depart in the direction 045 they tend to collide. starting on 04L it ends up on the 04R.

Would be nice if this problem would be checked.

greetz,

rob

Link to comment
Share on other sites

I confirm. Navdata Cycle 1401

kjfkprob.jpg

Airport data:

A,KJFK,KENNEDY INTL,40.639750,-73.778925,14,18000,18000,14500,0
R,04L,45,11351,150,1,110.900,45,40.622017,-73.785586,12,3.00,57,3,0
R,04R,45,8400,200,1,109.500,45,40.625425,-73.770347,12,3.00,53,3,0
R,13L,135,10000,150,1,111.500,135,40.656495,-73.787436,12,3.00,45,3,0
R,13R,135,14511,200,0,0.000,0,40.645495,-73.810386,13,3.00,50,3,0
R,22L,225,8400,200,1,110.900,225,40.645236,-73.754864,13,3.00,50,3,0
R,22R,225,11351,150,1,109.500,222,40.642433,-73.769636,13,3.00,59,3,0
R,31L,315,14511,200,1,111.350,315,40.632578,-73.781883,12,3.00,48,3,0
R,31R,315,10000,150,1,111.500,315,40.645170,-73.762458,13,3.00,49,3,0

Link to comment
Share on other sites

About the issue with runway offset. It was solved many many times, and I honestly have no idea why it keeps coming back. But don't worry, this time as usual I solved it and really hope it will never come back. But before I issue an update can you tell me if there are any strange behavior on approach or after landing? Airports that were affected in the past are for instance KJFK or BIKF.

Link to comment
Share on other sites

Please see if the arrivals are well aligned on the center-line during approach and if they stay on the runway after landing. If this is all okay then I can issue the update.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use