<AIXMBasicMessage gml:id="NMS_ID_NOTAM_1_80450756"><hasMember><event:Event gml:id="Event_1_NOTAM_1_80450756"><gml:identifier codeSpace="urn:uuid:">de349e6c-4d2a-4d6c-89e3-85f1dec08a14</gml:identifier><event:timeSlice><event:EventTimeSlice gml:id="Event_TS_1_NOTAM_1_80450756"><gml:validTime><gml:TimePeriod gml:id="Event_TS_TP_1_NOTAM_1_80450756"><gml:beginPosition>2026-03-19T00:00:00.000Z</gml:beginPosition><gml:endPosition indeterminatePosition="unknown"></gml:endPosition></gml:TimePeriod></gml:validTime><aixm:interpretation>BASELINE</aixm:interpretation><aixm:sequenceNumber>1</aixm:sequenceNumber><aixm:correctionNumber>0</aixm:correctionNumber><event:scenario>6000</event:scenario><event:textNOTAM><event:NOTAM gml:id="NOTAM_1_NOTAM_1_80450756"><event:series>A</event:series><event:number>1624</event:number><event:year>2026</event:year><event:type>N</event:type><event:issued>2026-05-05T03:56:45.000Z</event:issued><event:affectedFIR>LFMM</event:affectedFIR><event:selectionCode>QPUCH</event:selectionCode><event:traffic>I</event:traffic><event:purpose>BO</event:purpose><event:scope>A</event:scope><event:minimumFL>000</event:minimumFL><event:maximumFL>999</event:maximumFL><event:coordinates>4326N00513E</event:coordinates><event:location>LFML</event:location><event:effectiveStart>202603190000</event:effectiveStart><event:effectiveEnd>PERM</event:effectiveEnd><event:text>MANAGEMENT OF AIRCRAFT ON MISSED APPROACH ILS RWY31R : &#xA;IN THE PARTICULAR CASES OF A NAVIGATION ISSUE (TEMPORARY AIRCRAFT &#xA;INABILITY, LOSS OF GNSS SIGNAL, RNAV1-EXEMPTED AIRCRAFT), EVERY &#xA;AIRCRAFT UNABLE TO COMPLY WITH THE MISSED APCH PROCEDURE MUST REPORT &#xA;IT TO ATC AS SOON AS POSSIBLE AND COMPLY BY DEFAULT WITH THE &#xA;FOLLOWING BACK-UP PROCEDURE : &#xA;- CLIMB STRAIGHT AHEAD ON ALLOCATED RWY TRACK, UP TO RELATED MISSED &#xA;APCH PROCEDURE ALTITUDE, THEN ASK FOR RADAR VECTORING. &#xA;- OBST CLEARANCE IS PROVIDED UNTIL RADAR MINIMUM SAFETY ALTITUDE IN &#xA;COMPLIANCE WITH MISSED APPROACH MINIMUM SLOPE GRADIENT (2.5 PERCENT). &#xA;USE OF RNP X RWY31R (AR) AND RNP X RWY31L (AR) PROCEDURES TO REDUCE &#xA;THE NOISE IMPACT ON THE ENVIRONMENT DURING APPROACHES TO QFU 31, &#xA;QUALIFIED PILOTS OF AIR OPERATORS AUTHORIZED BY THE SUPERVISORY &#xA;AUTHORITY TO FLY RNP X RWY 31(AR) AND RNP X RWY 31L (AR) PROCEDURES &#xA;AT MARSEILLE PROVENCE WILL PREFERENTIALLY USE THESE PROCEDURES WHEN &#xA;QFU 31 IS DECLARED IN FORCE BY ATC. &#xA;TO THIS END, DURING INITIAL CONTACT WITH MARSEILLE PROVENCE APPROACH &#xA;CONTROL CENTER, PILOTS WILL ASK TO USE THE RNP X (AR) PROCEDURE &#xA;ASSOCIATED WITH THE RUNWAY IN USE (RWY 31R OR RWY 31L). &#xA;WARNING: THE FINAL APPROACH SLOPES FOR THE RNP X RWY 31R (AR) AND RNP &#xA;X RWY 31L (AR) PROCEDURES ARE DIFFERENT FROM THE PAPI SETTING. WITH &#xA;GROUND TEMPERATURES BELOW 15 DEGREES CELSIUS, 4 REDS MAY BE DISPLAYED &#xA;ON THE PAPI. &#xA;NOTA BENE: THE RNP X RWY 31R (AR) AND RNP X RWY 31L (AR) PROCEDURES &#xA;ARE APPROACH PROCEDURES DESIGNED IN ACCORDANCE WITH THE RNP AR APCH &#xA;NAVIGATION SPECIFICATION.) PUBLIC (NON-PRIVATE) RNP AR PROCEDURES, FULLY COMPLIANT WITH THE &#xA;CRITERIA OF THE 3RD EDITION OF ICAO DOCUMENT 9905. &#xA;THE RNP AR APPROVAL MUST BE ISSUED BY THE OPERATOR&#39;S REGULATORY &#xA;AUTHORITY, ALONG WITH A CERTIFICATE INDICATING THAT THE RNP AR &#xA;APPROVAL HAS BEEN ISSUED IN ACCORDANCE WITH ICAO DOC 9997. &#xA;REF. AD 2 LFML.AD 2.22.2.1)</event:text><event:translation><event:NOTAMTranslation gml:id="NT_1_NOTAM_1_80450756"><event:type>OTHER:ICAO</event:type><event:formattedText><html:div>180729 EUECYIYN  NOTAM REPLACED BY A2825/26  ORIGINAL NOTAM  (A1624/26 NOTAMN  Q) LFMM/QPUCH/I /BO /A /000/999/4326N00513E005  A) LFML B) 2603190000 C) PERM E) MANAGEMENT OF AIRCRAFT ON MISSED APPROACH ILS RWY31R :  IN THE PARTICULAR CASES OF A NAVIGATION ISSUE (TEMPORARY AIRCRAFT  INABILITY, LOSS OF GNSS SIGNAL, RNAV1-EXEMPTED AIRCRAFT), EVERY  AIRCRAFT UNABLE TO COMPLY WITH THE MISSED APCH PROCEDURE MUST REPORT  IT TO ATC AS SOON AS POSSIBLE AND COMPLY BY DEFAULT WITH THE  FOLLOWING BACK-UP PROCEDURE :  - CLIMB STRAIGHT AHEAD ON ALLOCATED RWY TRACK, UP TO RELATED MISSED  APCH PROCEDURE ALTITUDE, THEN ASK FOR RADAR VECTORING.  - OBST CLEARANCE IS PROVIDED UNTIL RADAR MINIMUM SAFETY ALTITUDE IN  COMPLIANCE WITH MISSED APPROACH MINIMUM SLOPE GRADIENT (2.5 PERCENT).  USE OF RNP X RWY31R (AR) AND RNP X RWY31L (AR) PROCEDURES TO REDUCE  THE NOISE IMPACT ON THE ENVIRONMENT DURING APPROACHES TO QFU 31,  QUALIFIED PILOTS OF AIR OPERATORS AUTHORIZED BY THE SUPERVISORY  AUTHORITY TO FLY RNP X RWY 31(AR) AND RNP X RWY 31L (AR) PROCEDURES  AT MARSEILLE PROVENCE WILL PREFERENTIALLY USE THESE PROCEDURES WHEN  QFU 31 IS DECLARED IN FORCE BY ATC.  TO THIS END, DURING INITIAL CONTACT WITH MARSEILLE PROVENCE APPROACH  CONTROL CENTER, PILOTS WILL ASK TO USE THE RNP X (AR) PROCEDURE  ASSOCIATED WITH THE RUNWAY IN USE (RWY 31R OR RWY 31L).  WARNING: THE FINAL APPROACH SLOPES FOR THE RNP X RWY 31R (AR) AND RNP  X RWY 31L (AR) PROCEDURES ARE DIFFERENT FROM THE PAPI SETTING. WITH  GROUND TEMPERATURES BELOW 15 DEGREES CELSIUS, 4 REDS MAY BE DISPLAYED  ON THE PAPI.  NOTA BENE: THE RNP X RWY 31R (AR) AND RNP X RWY 31L (AR) PROCEDURES  ARE APPROACH PROCEDURES DESIGNED IN ACCORDANCE WITH THE RNP AR APCH  NAVIGATION SPECIFICATION.) PUBLIC (NON-PRIVATE) RNP AR PROCEDURES, FULLY COMPLIANT WITH THE  CRITERIA OF THE 3RD EDITION OF ICAO DOCUMENT 9905.  THE RNP AR APPROVAL MUST BE ISSUED BY THE OPERATOR&#39;S REGULATORY  AUTHORITY, ALONG WITH A CERTIFICATE INDICATING THAT THE RNP AR  APPROVAL HAS BEEN ISSUED IN ACCORDANCE WITH ICAO DOC 9997.  REF. AD 2 LFML.AD 2.22.2.1)</html:div></event:formattedText></event:NOTAMTranslation></event:translation></event:NOTAM></event:textNOTAM><event:extension><fnse:EventExtension gml:id="FNSE_1_NOTAM_1_80450756"><fnse:classification>INTL</fnse:classification><fnse:accountId>LFFAYNYX</fnse:accountId><fnse:airportname>MARSEILLE-PROVENCE</fnse:airportname><fnse:originID>EUECYIYN</fnse:originID><fnse:qline>LFMM/QPUCH/I /BO /A /000/999/4326N00513E005</fnse:qline><fnse:lastUpdated>2026-05-05T03:56:00.000Z</fnse:lastUpdated><fnse:icaoLocation>LFML</fnse:icaoLocation></fnse:EventExtension></event:extension></event:EventTimeSlice></event:timeSlice></event:Event></hasMember><hasMember><aixm:AirportHeliport gml:id="AH_1_NOTAM_1_80450756"><gml:identifier codeSpace="urn:uuid:">c0800589-8323-42a0-b074-a18795f41728</gml:identifier><aixm:timeSlice><aixm:AirportHeliportTimeSlice gml:id="AH_TS_1_NOTAM_1_80450756"><gml:validTime><gml:TimeInstant gml:id="AH_TS_TI_1_NOTAM_1_80450756"><gml:timePosition>2026-05-05T03:56:00.000Z</gml:timePosition></gml:TimeInstant></gml:validTime><aixm:interpretation>SNAPSHOT</aixm:interpretation><aixm:designator>LFML</aixm:designator><aixm:name>MARSEILLE-PROVENCE</aixm:name><aixm:locationIndicatorICAO>LFML</aixm:locationIndicatorICAO><aixm:ARP><aixm:ElevatedPoint gml:id="EP_1_NOTAM_1_80450756" srsName="urn:ogc:def:crs:EPSG::4326" srsDimension="2"><gml:pos>43.436667 5.215000</gml:pos></aixm:ElevatedPoint></aixm:ARP><aixm:extension><event:AirportHeliportExtension gml:id="AHE_EVENT_1_NOTAM_1_80450756"><event:theEvent xlink:href="#Event_1_NOTAM_1_80450756"></event:theEvent></event:AirportHeliportExtension></aixm:extension></aixm:AirportHeliportTimeSlice></aixm:timeSlice></aixm:AirportHeliport></hasMember></AIXMBasicMessage>