Iv just flown a 3 hour flight from Heathrow to JFK in the SSTSIM. (Taken me weeks to nail that, i tell ya!)So, there I was at FL580 at Mach 2, when RC bought me down and started to vector me to Final.Following the vectors and i was told to intercept the Localiser. The thing is, i was vectored to cross it too far for my trusty nav radios to see it, and i shot straight passed it. So, i filed a missed approach and went round again. This time RC had me come in from another direction (based on my position when i called the missed approach).Same thing happened... So after a few F words (and the missus telling me off for swearing in earshot of the kids :( ), i tried it again. Still no luck. I gave my monitor a piece of my mind and quit the sim. Seems like a good idea at the time - kinda getting my own back, but wishing i didnt now. My thinking is that i would try to edit the AFCAD of KJFK. And sure enough, the ILS on runway 04L is only 27nm long, and RC seems to be getting me abour 35nm from the LOC.Is it possible to lengthen the ILS to say 40nm in AFCAD? Or am i using RC wrong? Please note that the Concorde doesnt have a graphical nav like a Boeing or Airbus, nor does it have a GPS, so i cant change my heading to get me closer. And for an auto landing, both navs need to be tuned into the ILS freq.Please help! Im only 20 years old and i have clumps of hair missing from trying to work this out. :(EDIT - I also done a different flight ages ago where i was vectored too CLOSE to the runway...

You can monitor with NAV2 the JFK VOR which is roughly near the runways with the OBS set to the inbound heading. When the "TO" reading is near the inbound LLZ reading turn inbound homing on the VOR still and wait until the LLZ comes alive on the NAV 1 (tuned to the LLZ) and start following it. By having the LLZ frequency on standby in NAV 2 you can then switch it active to put NAV 2 on the LLZ for your second required receiver for a fully coupled approach. You'll be near enough to the inbound LLZ track when it comes alive still several miles out. In addition if the VOR has a DME that can be handy to roughly gauge your distance to the airport and also for avionics of that generation to establish your forty mile radius to insure you'll meet the crossing restriction.The AFCAD I have shows that both ends of most runways at JFK share the same ILS frequency either the same or adjacent runway. Use AFCAD for a "standard or default" AFD property file to list NAVAIDS and turn off the backcourse of the LLZs, on by default in FS. As you fly around the approach pattern this can prevent a false back indication from the incorrect LLZ. In the real world in such shared frequency cases only the active runway LLZs would be turned on. Always check either the audio Morse code ident (it's on the approach plate) or IDENT read out if available to ensure you are on the correct LLZ especially before engaging the AP coupling. Without turning off the backcourse you usually see the incorrect LLZ until within about two degrees of the extended center line.

Iv just flown a 3 hour flight from Heathrow to JFK in the SSTSIM. (Taken me weeks to nail that, i tell ya!)So, there I was at FL580 at Mach 2, when RC bought me down and started to vector me to Final.Following the vectors and i was told to intercept the Localiser. The thing is, i was vectored to cross it too far for my trusty nav radios to see it, and i shot straight passed it. So, i filed a missed approach and went round again. This time RC had me come in from another direction (based on my position when i called the missed approach).Same thing happened... So after a few F words (and the missus telling me off for swearing in earshot of the kids :( ), i tried it again. Still no luck. I gave my monitor a piece of my mind and quit the sim. Seems like a good idea at the time - kinda getting my own back, but wishing i didnt now. My thinking is that i would try to edit the AFCAD of KJFK. And sure enough, the ILS on runway 04L is only 27nm long, and RC seems to be getting me abour 35nm from the LOC.Is it possible to lengthen the ILS to say 40nm in AFCAD? Or am i using RC wrong? Please note that the Concorde doesnt have a graphical nav like a Boeing or Airbus, nor does it have a GPS, so i cant change my heading to get me closer. And for an auto landing, both navs need to be tuned into the ILS freq.Please help! Im only 20 years old and i have clumps of hair missing from trying to work this out. :(EDIT - I also done a different flight ages ago where i was vectored too CLOSE to the runway...