Jump to content

Search the Community

Showing results for tags 'codes'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • General Forum
  • Aircraft
    • Concorde-X
    • A3xx Master Series
    • Screenshots
  • Tools
    • FSL Hardware Interface
    • FSL Control Center
    • FSL Spotlights
  • Cockpit Building
    • Chat about cockpit building
  • easyJet Crew's easyForum
  • British Airways's The BA Club
  • AVIANCA's FORUM
  • Aegean Airlines's The Pub of Accord
  • Wizz Air's Topics
  • My little software corner's Developments

Categories

  • A319-X Liveries
    • PBR User Submitted Liveries
    • Older Non PBR Liveries
  • A320-X Liveries
    • Older non PBR Liveries
    • FSX & P3Dv3 Liveries
  • A321-X Liveries
    • User Submitted Liveries
  • A3XX Misc Files
    • Cabin Textures
    • EFB Backgrounds
    • A320-X - Unsupported Mods
    • Utilities
  • Concorde-X Files
  • FSL Aircraft Paint Kits
  • Spotlights
  • Hardware Interface for Prepar3D v4 & v5
  • Legacy Interfaces
  • Olympic Air Virtual's Files
  • Wizz Air's Files
  • Eurowings Crew's Configs / Textures / Sounds
  • Eurowings Crew's Operational Files
  • My little software corner's Downloads

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 1 result

  1. Jonathan Fong

    Concorde ICAO Equipment Codes

    Recently, I've been working on updating quite a few of the old Concorde flight plans to be compatible with modern-day AIRACs - you can see the results of said work in the Concorde Routes in Current AIRACs pinned thread (I'm collaborating with @petakas on the routes). Since I was already looking at the routes, I thought - why not update Concorde's flight plan remarks too? As you may know, there have been quite a few revisions to the ICAO equipment code definitions since Concorde last flew, so I thought I'd try my hand at matching Concorde's equipment to the modern-day equipment code definitions to file to VATSIM/IVAO. Here are the revised remarks, organized in proper order and format as per the ICAO flight plan format (by item number). Allow me to explain what all that means. The first row is for items 10a/10b of the ICAO flight plan format, denoting navigational equipment and surveillance equipment capability respectively. H denotes the 'heavy' wake turbulence category, of which Concorde was classified under. S indicates VHF RTF, VOR, and ILS capaiblity, D indicates DME capability, F ADF capability, I inertial navigation, R that the plane is PBN approved (see PBN section), W that the plane is RVSM capable, and X that it is MNPS compliant. The surveillance code - C - indicates that Concorde's transponder was MODE A/MODE C capable. NOTE: The original Concorde flight plans also contained the equipment code Y, which back then was simply defined as "when ATS (Air Traffic Services) requires it" from my sources, which is quite vague, but nowadays denotes VHF radio 8.33kHz spacing capability. According to my sources, BA's Concordes were not 8.33kHz equipped; however, I have not been able to find any definitive information regarding AF's Concordes' radios though it would be presumed they had them near the end of their service life as France adopted mandatory 8.33kHz spacing above FL245 in 1999. If you wish to file your flight plan as 8.33kHz equipped, just type in Y after X in the Item 10a section above when filing the flight plan, like this - The next row is for Item 18 of the ICAO flight plan - the additional information section. PBN/A1B5 denotes Concorde's RNAV10 and RNAV 5 (INS) capability, while SUR/TCAS indicates Concorde has TCAS surveillance capability. DOF/ indicates the date of flight in YYMMDD format, while REG/ indicates the registration - change this on a per-aircraft basis (NOTE: Do NOT include the dash when changing the registration. Write it in this format - GBOAF or FBTSD). EET/ is the estimated time to waypoint - this field can be omitted if you don't have access to such figures, although you can usually find old EET figures which should be mostly accurate from old Concorde flight plans here. SEL/ is the SELCAL of the aircraft - again, change this accordingly depending on which specific aircraft you are flying (and as with the registration, do NOT include the dash e.g. SEL/BDFH or SEL/AGEJ). RMK/LAHSO NOT AUTHORIZED simply indicates that Concorde is not authorized for LAHSO by its operator (AF and/or BA), while RVR/075 indicates the aircraft is capable of performing a CATIII autoland. If you are filing on VATSIM, file your aircraft as H/CONC/I - H denotes heavy wake turbulence as mentioned above, while the code I (not the same code as above - this is using the FAA system) denotes INS-based RNAV navigation. File the above remarks (including ICAO flight plan code) in the remarks section as one line, like this - If you are filing on IVAO, simply enter the appropriate codes into each section of the flight plan window given in IvAp. As mentioned previously, Items 10a/10b go into the Item 10 section while the Item 18 line goes into Item 18. If you find any inconsistencies, please let me know so I can modify the remarks accordingly.
×
×
  • Create New...