← back

!! NOT FOR OPERATIONAL USE !! data may be stale, incomplete, or wrong

raw text:

REF AD 2 -GCFV AD  WEF 09-JUL-26.
GCFV AD 2.22  FLIGHT PROCEDURES: ADD THE FOLLOWING INFORMATION:
ALTERNATIVE PROCEDURES FOR AIRCRAFT NOT EQUIPPED WITH RNAV1.
1.ARRIVAL TO FUERTEVENTURA:
AIRCRAFT WITHOUT RNAV1 OPERATIONAL APPROVAL WILL NOTIFY ATC WHEN 
THEY ARE CLEARED FOR THE CORRESPONDING RNAV1 STAR, AND WILL AWAIT 
ALTERNATIVE TACTICAL INSTRUCTIONS FROM CANARIAS APP.
2. DEPARTURES FROM FUERTEVENTURA:
DEPARTING AIRCRAFT WITHOUT RNAV1 OPERATIONAL APPROVAL THAT ARE 
PLANNING TO PROCEED VIA AN EXCLUSIVE RNAV1 DEPARTURE ROUTE 
WILL NOTIFY FUERTEVENTURA TWR VIA VOICE COMMUNICATION AS SOON 
AS POSSIBLE AND WILL BE INSTRUCTED TO PROCEED IN ACCORDANCE 
WITH THE CONTINGENCY DEPARTURES (SEE CONTINGENCY DEPARTURE 
(ODP) FOR THE RUNWAY IN USE AT AD2 SID GCFV)

icao text:

B8727/26 NOTAMN
 Q) GCCC/QPICH/I /NBO/A /000/999/2827N01352W005
 A) GCFV B) 2610231120 C) PERM
 E) REF AD 2 -GCFV AD  WEF 09-JUL-26.
 GCFV AD 2.22  FLIGHT PROCEDURES: ADD THE FOLLOWING INFORMATION:
 ALTERNATIVE PROCEDURES FOR AIRCRAFT NOT EQUIPPED WITH RNAV1.
 1.ARRIVAL TO FUERTEVENTURA:
 AIRCRAFT WITHOUT RNAV1 OPERATIONAL APPROVAL WILL NOTIFY ATC WHEN 
 THEY ARE CLEARED FOR THE CORRESPONDING RNAV1 STAR, AND WILL AWAIT 
 ALTERNATIVE TACTICAL INSTRUCTIONS FROM CANARIAS APP.
 2. DEPARTURES FROM FUERTEVENTURA:
 DEPARTING AIRCRAFT WITHOUT RNAV1 OPERATIONAL APPROVAL THAT ARE 
 PLANNING TO PROCEED VIA AN EXCLUSIVE RNAV1 DEPARTURE ROUTE 
 WILL NOTIFY FUERTEVENTURA TWR VIA VOICE COMMUNICATION AS SOON 
 AS POSSIBLE AND WILL BE INSTRUCTED TO PROCEED IN ACCORDANCE 
 WITH THE CONTINGENCY DEPARTURES (SEE CONTINGENCY DEPARTURE 
 (ODP) FOR THE RUNWAY IN USE AT AD2 SID GCFV)

downloads:

• raw AIXM 5.1 XML
• GeoJSON Feature

!! NOT FOR OPERATIONAL USE !! data may be stale, incomplete, or wrong

© 2026 coredoes.dev