Traffic Management of Non-Reduced Vertical Separation Minima (RVSM) Aircraft Operating in RVSM Airspace

1. SOP Traffic Management of Non-Reduced Vertical Separation Minima (RVSM) Aircraft Operating in RVSM Airspace • Symbology used: • Begin point • Decision/option point • Action • End • Note • Facility/Area-specific Standard Operating Procedures DRAFT 25MAR04 -- DRAFT

2. File and operate per existing LOA and SOPs [LOA exists for this Flight Op] [Pre-coordination for ‘non-RVSM in RVSM airspace’] [Unable to approve ‘non-RVSM in RVSM airspace’] Operator contacts Departure ARTCC to request approval Advise ‘requestor’ with reason for disapproval & document TMU documents, analyzes, coordinates request, per facility SOPs [MIL File & Go Option is OK] [Non-RVSM flight in RVSM airspace ‘conditionally approved’ by affected areas] TMU documents feedback from areas re. the flight [Unable to approve or approval needs to be withdrawn] ARTCC advises requestor per SOP of “conditional approval” to operatein RVSM airspace Requestor files flight plan TMU & OS/CIC continuously monitor conditional approvals and traffic flow in general OS/CIC notifies TMUasap Some sort of “disclaimer” is likely re: EFC, time, “traffic permitting”, etc. [No other options] TMU coord. with Areas to identify alternative actions SOP SOP [Traffic flow/scenario looks acceptable for the ‘non-RVSM’ flight in RVSM airspace] SOP SOP SOP SOP SOP [Unable to approve or approval needs to be withdrawn] Notify affected areas; work aircraft per usual SOP Facility analyzes ability to accommodate the non-RVSM aircraft Flight departs OK 25MAR04 -- DRAFT Traffic Management of Non-Reduced Vertical Separation Minima (RVSM) Aircraft Operating in RVSM AirspaceIntra-Facility Coordination DRAFT

3. Prior coord.60 – 240 min before P-time [Not all ARTCCs able to approve non-RVSM] Operator contacts ATCSCC directly with request to operate in RVSM airspace prior to departure All affected ARTCCs analyze request for impact on their tfc flow ATCSCC logs request & forwards to all affected ARTCCs [No options exist] [Other ALT/RTEoptions exist] ATCSCC coordinates other options with affected ARTCCs [Non-RVSM flight in RVSM airspace is conditionally approved by all affected ARTCCs] ATCSCCdocuments disapproval; notifies ‘requestor’, TMU & all other affected ARTCCs. [Other options exist] Requestor isnotified of‘conditional’ approval [No other options exist] ATCSCC documents approval & notifies all affected ARTCCs TMUs continuously monitor RVSM and non-RVSM requests Requestor files (or revises)Flight Plan [Tfc changes; approval withdrawn] Some sort of “disclaimer” likely re: VIFNO, time, EFC, “traffic permitting”, etc. [Traffic flow/scenario still looks acceptable for the multi-Center non-RVSM flight in RVSM] [Tfc changes; approval withdrawn] Flight departs SOP SOP SOP TMU advises ATCSCC asap SOP [Pre-coordinated] [MIL ‘File & Go’ Flt; not pre-coordinated] TMU documents request; contacts ATCSCCfor coord. help ARTCCs assign requested ALT when traffic permits per usual SOP All affected ARTCCs analyze current tfc with ‘non-RVSM’ impact [Still OK] 25MAR04 -- DRAFT Traffic Management of Non-Reduced Vertical Separation Minima (RVSM) Aircraft Operating in RVSM AirspaceInter-Facility Coordination DRAFT