Critical Flight Zone

Owned by Diego Cesa de Meira (Unlicensed)
Sept 05, 2019
1 min read

Description

Critical Flight Zone (CFZ)Airspace within a 10-nautical-mile (nm) radius of the Airport Reference Point (ARP), up to and including 10,000 feet AGL, where a level of laser light is restricted to avoid flash blindness or after image effects.

Credit: Image courtesy of Federal Aviation Administration

Originator

  1. Transport Canada

  2. Nav Canada

Use Cases

  1. As an Aviation Enforcement Officer, I want to be able to know the extent of CFZ so that regulation can be strictly enforced to ensure aircraft safety.

Source(s)

Description

Source

Format

Date

Update Frequency

Metadata

Cost

Link

Remarks

Description

Source

Format

Date

Update Frequency

Metadata

Cost

Link

Remarks

Critical Flight Zone (CFZ)

Transport Canada
NavCan

CSV
PDF

2018

On-going

N/A

Free

EGIS Data Folder: CriticalFlightZone_Airport.gdb.zip
CriticalFlightZone_Boundary.gdb.zip
PDF

-Use preprocessed GDB file as provided.
-Canada Airport Database extracted from CFS

Remarks

  1. LFZ is created using FME based on FAA Critical Flight Zone standards.

  2. EGIS Data Folder: \\ncras382\Application Source Files\EGIS\Smartmap Files\

Process for EGIS integration

Creating CFZ Model:

  1. In FME, transform Airport Reference Point (ARP) in Canada Airport database to point.

  2. Create 10 NM buffer around ARP.

    Credit: Image courtesy of Federal Aviation Administration

  3. Assign elevation of 10,000' AGL and extrude the 3D model.

  4. Output to KML, SHP or GDB as required

  5. Import into EGIS

Process for EGIS integration

TC Smart Maps:

  1. Not all GIS applications can consume KML file directly due to its unique data structures such as networklinks, folders, models etc.

  2. Please contact Lawrence Chong, Digital Services Directorate for TC Smart Maps KML dataset and format translation.

  3. TC Smart Maps KML link: \tc.gc.ca\tcgis\GISData\Google Mashup\Aerodrome\CriticalFlightZone\CriticalFlightZone.kmz

Customization:

  1. Schema transformation: As required

  2. Denormalization: Not required

  3. Value coding: Not required

  4. Attribute renaming: As required to improve readability

  5. Attribute removal: It is highly recommended as some fields are unnecessary, this will also reduce file size and improve performance

  6. Geoenrichment: Feature symbolization is recommended to improve visualization. Extrude the 3D model where applicable.

  7. Format translation: Not required

  8. Language translation: French version not available

  9. Update frequency: As identified