Mike Sweeney

Night departure procedures for turbine aircraft are often designed for noise abatement. (routing departing jet aircraft over less noise-sensitive areas at night). A less-efficient (more track miles) 2T departure does not appear based on lower-traffic-volume at night.

For runway 06, this might also help prepare what to expect, .... "narrow down the SID further" (c) Navigraph

US airspace class G similar to UK = No IFR clearance and no ATC communication requirements for uncontrolled airspace. ... in practical terms, most US airspace abv 700' or 1200' AGL is controlled (class E or better).

When cleared for the ILS approach, maintain 4,600 until intercept, descend on the glide slope. © Navigraph For questions about ATC services, consider contacting the vACC directly. *- To locate vACC contacts, www.vatsim.net | select About and click VATSIM Regions| click on Europe Region | select the Division | navigate to the relevant vACC website link. example list. Hope this helps.

Local vACCs often include Pilot Briefing information on their website. Consider also posting Pilot Briefing link on Italian vACC website.

If you have FSInn, traffic can be displayed out to 120nm, or reduced to a 2nm scale, with ADS-B In type information, (Aircraft ID/callsign, ground speed, position, altitude, direction of flight). InnRadar examples attached (... with a comparison for TCAS display). -Alternatively, refer to similar in Andreas' SWIFT illustration above.

Coordinates for waypoints (former SM track), it appears oceanic random route: (LESLU) 5041N01500W 5050N02000W 5030N03000W 4916N04000W 4703N05000W (SM waypoint identifiers, SM15W, etc, have been retired) Also consider filing and other information here: Concorde Routes In Current Airacs [updated through 2017; thanks Kyp!] For the follow-up questions, legacy info might also be useful: - Concorde Flight Plans, Concorde Pilot Procedures (dated/external)

As above, pilots refer to the altitudes/flight level on a STAR with a line above, below, or both. For 'descend via' clearance, cross ABASN at/abv FL270 Other altitudes (the min route altitudes on a segment of the SSKII arrival) are not relevant for a 'descend via' clearance, .... as a side note for US airspace, questions have been raised by rw pilots and re-visited by the FAA. The criteria for determining an MEA on an en-route chart may not be the same as a minimum route altitude for a segment published on a STAR. - MEA (Minimum Enroute IFR Altitude) 'lowest published altitude between radio fixes that ensures acceptable navigational signal coverage and meets obstacle clearance requirements between those fixes'. - On a STAR (or SID), minimum route altitudes for a segment may have been "artificially raised to support ATC separation needs/traffic management". (pilot may reference in the event of an aircraft emergency + radio failure/ lost comms ... additional in two links above.) In case useful ... - Aeronautical Chart User's Guide (pages 119, 123) - Aeronautical Information Manual (check 5-4-1, Standard Terminal Arrival (STAR) Procedures; "descend via" examples)

For the departure airport, real world there is nothing which precludes filing an IFR flight plan, calling for a clearance, obtaining a release; ATC protects the airspace. If an IFR arrival has already been cleared for the rnav 20 approach, Montreal holds the departure (IFR release) until the landing aircraft cancels IFR. (one in/one out) For obstructions and alert airspace, refer to departure procedures and climb rate, as published. © navigraph/ jeppesen 10-9 A composite flight plan, with wx requirements for a VFR departure ... not necessary. [Vis 1/2 or better; file IFR]

JUTEK V487 BTV appears ok for online flight simulation or ... For IFR, consider CSU3 CFWSH V487 BTV KMPV at 8,000 For VFR (weather permitting), dct at 7,500 - (In rw, land at airport of entry KBTV; for simulation, CBP irrelevant) In case you are checking replies Alexander, hope this helps.

Many thanks for (a) inviting feedback and (b) such positive responses! Great job ... and appreciated.

"we have people on the team experienced with maintaining it and making changes to the theme, etc." Looking forward to user-selected theme options, links from google fixed, post preview, save draft, etc ... features available before the upgrade.

Same question, was a change necessary?

Hi Jose, To remove display of duplicates, see whether this helps ... In ServInfo, click on Options and select 'Display Preferences'. In the popup box, check the box for 'Hide Prefiled'. Click OK. Reload the data by clicking on the VATSIM button (top left).

Wherever servinfo has been installed on the computer, there should be a folder called si202, or similar. The servinfo.ini file is in that folder. When searching the computer's hard drive using windows, did it find servinfo.ini? Was it possible to open servinfo.ini using Notepad or some equivalent? Was the ServInfo application closed before making the change to servinfo.ini? Was the line (VATSIM Servers Locator) changed in servinfo.ini as described, saved, and then closed, and then re-start Servinfo? Was the existing line changed as described, or was a new line inserted as an additional line? "Update the line to indicate" means: Change FROM: VATSIM Servers Locator Url=http://status.vatsim.net/data Change TO: [ConnectionParameters] VATSIM Servers Locator Url=http://status.vatsim.net/ Hope this helps.