alpha117

Members
  • Content count

    900
  • Joined

  • Last visited

About alpha117

  • Rank
    Multi-Crew Experience
  • Birthday 09/04/1958

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

Profile Information

  • Gender
    Male
  • Location
    Lincolnshire,UK

Recent Profile Visitors

2,110 profile views
  1. Thanks Oliver
  2. Glad it is not just me I'll disable this function until Keven comes up with a solution Thanks
  3. Hi Keven Automatically Thanks
  4. Hi All Perhaps a very simple answer, but when CP goes into this mode how do you get back to 'normal'. I tried select different internal cameras but it just switch external views Something simple that I have missed Thanks
  5. Hi Oliver The reason I did that was due to testing with SimStarter.
  6. Morning Oliver, Get this when importing external cfg Also, I've taken the scenery.cfg from the backup.zip and overwritten the one in Program Data. How can I get the program to see the 'new' scenery.cfg. (Refresh)? Thanks
  7. Thanks Oliver, That's made it clearer
  8. Hi All, Just wondering if this is 'good' practice to have more than one airport in the same add-on.xml. Also, what is the maximum add-on.xml's you can have? thanks
  9. Many Thanks Oliver Now back up and running
  10. Hi All Has been OK since day one, but now for some strange reason, start the .exe and nothing happens. Not sure what has changed. I've uninstalled and reinstalled but still the same issue.File does not even appear in Task Manager Any pointer would be good Using latest version Thanks Clive
  11. Hi All All the others work OK, but for some strange reason this one does not work for me. Any ideas? Thanks Clive
  12. This route(PFPX) goes though the TFR TEB V214 DIRMY V213 RBV DCT CYN DCT VCN V184 ACY They(TFR) appear in the NOTAM in PFPX │KSMQ (SOMERSET, UNITED STATES) UTC -04:00│ └──────────────────────────────────────────────────────────────────────────────┘ 08/033 AIRSPACE SEE FDC 7/3067 ZDC 91.141 VIP TFR. 18 AUG 20:00 2017 UNTIL 21 AUG 00:30 2017. CREATED: 17 AUG 04:07 2017 08/032 AIRSPACE SEE FDC 7/3062 ZNY 91.141 VIP TFR. 18 AUG 20:00 2017 UNTIL 21 AUG 00:30 2017. CREATED: 17 AUG 04:07 2017 08/031 AIRSPACE SEE FDC 7/3061 ZBW 91.141 VIP TFR. 18 AUG 20:00 2017 UNTIL 18 AUG 22:00 2017. CREATED: 17 AUG 04:02 2017 08/030 AIRSPACE SEE FDC 7/3060 ZNY 91.141 VIP TFR. 18 AUG 20:00 2017 UNTIL 18 AUG 22:00 2017. CREATED: 17 AUG 04:02 2017 08/029 AIRSPACE SEE FDC 7/3050 ZBW 91.141 VIP TFR. 18 AUG 14:30 2017 UNTIL 18 AUG 16:30 2017. CREATED: 17 AUG 04:02 2017 08/028 AIRSPACE SEE FDC 7/3049 ZNY 91.141 VIP TFR. 18 AUG 14:30 2017 UNTIL 18 AUG 16:30 2017. CREATED: 17 AUG 04:02 2017 08/027 AIRSPACE SEE FDC 7/1583 ZNY 91.141 VIP TFR. 16 AUG 17:45 2017 UNTIL 21 AUG 00:30 2017. CREATED: 15 AUG 15:15 2017 08/026 AIRSPACE SEE FDC 7/1582 ZDC 91.141 VIP TFR. 16 AUG 17:45 2017 UNTIL 21 AUG 00:30 2017. CREATED: 15 AUG 15:14 2017 The FDC reference is here: https://www.nbaa.org/ops/airspace/alerts/notams/vip-tfrs/ So, I think it is a company dispatch job after reading the NOTAMS to re plan the route
  13. Hi Tony This interests me, never heard of TFR before, perhaps I'm in the UK and that is why! Anyway I found this : https://www.aircharteradvisors.com/presidential-tfr-new-jersey/ In your case would you not just re-file the FP to take you around the TFR or is it an ATC 'thing' that vectors around the TFR, I've no idea but would like to know. Also P2A would expect you to follow your filed FP, hence the 'unable'. P2A is not aware of any TFR as they are not in the AIRAC data. When you headed west did P2A tell you to 'turn heading' or anything else? Could you post the FP's that you filed with P2A, thanks Can anyone else chime in here with more details on how TFR's and ATC works in the realworld etc, would be good The 'Also I think ATC should respect a pilots response of "unable".' ATC can 'see' more than the pilot and there would have to be a very good reason why the pilot is unable. Yes in this case it was the TFR, which ATC is not aware of Thanks Clive
  14. Can confirm that this has been tested and fixed in the next update
  15. Can confirm this has been tested and fixed in next update