# US 2026/0311600 A1 · Trajectory-based operations flight plan submission systems and methods

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0311600 A1
- Document ID: US20260311600A1
- Status: Published application
- Kind: A1
- Application number: 19/098,341
- Filed: 2025-04-02
- Published: 2026-10-08
- Earliest claimed: 2025-04-02
- Assignees: The Boeing Company
- Applicants: The Boeing Company
- Inventors: Ítalo Romani de Oliveira; Pablo Costas Álvarez; Stephen Solomon Altus; Carlos Sánchez Barberán
- Web page: https://patentgrep.com/patent/US20260311600A1

## CPC

- G08G 5/32: for flight plan preparation
- G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93})

## Abstract

A system and a method include a control unit configured to receive a flight plan for an aircraft. The flight plan is in a first data standard. The control unit is further configured to convert the flight plan in the first data standard into the flight plan in a second data standard. The second data standard differs from the first data standard.

## Claims

### Claim 1

A system comprising:
a control unit configured to:
receive a flight plan for an aircraft, wherein the flight plan is in a first data standard, and
convert the flight plan in the first data standard into the flight plan in a second data standard, wherein the second data standard differs from the first data standard.

### Claim 2 (depends on 1)

The system of claim 1, wherein the first data standard is one of extensible markup language (XML), JavaScript Object Notation (JSON), Plain Text (TXT), or Portable Document Format (PDF).

### Claim 3 (depends on 2)

The system of claim 2, wherein the second data standard is Flight-and-Flow Information for Collaborative Environment (FF-ICE).

### Claim 4 (depends on 1)

The system of claim 1, wherein the control unit is further configured to submit the flight plan in the FF-ICE standard to an FF-ICE filing service, and interpret a reply from the FF-ICE filing service.

### Claim 5 (depends on 1)

The system of claim 1, wherein the control unit is further configured to convert the flight plan in the first data standard into a flight information exchange model (FIXM) flight plan format by, at least in part, creating a globally unique flight identifier (GUFI).

### Claim 6 (depends on 1)

The system of claim 1, wherein the control unit is configured to receive the flight plan in the first data standard from a computerized flight-plan system.

### Claim 7 (depends on 1)

The system of claim 1, further comprising a user interface including a display and an input device, wherein the control unit is in communication with the user interface, and wherein the control unit is further configured to show the flight plan in one or both of the first data standard or the second data standard on the display.

### Claim 8 (depends on 7)

The system of claim 7, wherein the control unit is further configured to show a route comparison on the display.

### Claim 9 (depends on 1)

The system of claim 1, further comprising a communication device coupled to the control unit, wherein the control unit is configured to receive the flight plan in the first data standard and output the flight plan in the second data standard via the communication device.

### Claim 10 (depends on 1)

The system of claim 1, further comprising the aircraft, wherein the aircraft is configured to be operated according to the flight plan in the second data standard.

### Claim 11

A method comprising:
receiving, by a control unit, a flight plan for an aircraft, wherein the flight plan is in a first data standard; and
converting, by the control unit, the flight plan in the first data standard into the flight plan in a second data standard, wherein the second data standard differs from the first data standard.

### Claim 12 (depends on 11)

The method of claim 11, wherein the first data standard is one of extensible markup language (XML), JavaScript Object Notation (JSON), Plain Text (TXT), or Portable Document Format (PDF), and wherein the second data standard is Flight-and-Flow Information for Collaborative Environment (FF-ICE).

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
submitting, by the control unit, the flight plan in the FF-ICE standard to an FF-ICE filing service; and
interpreting, by the control unit, a reply from the FF-ICE filing service.

### Claim 14 (depends on 11)

The method of claim 11, further comprising converting, by the control unit, the flight plan in the first data standard into a flight information exchange model (FIXM) flight plan format by, at least in part, creating a globally unique flight identifier (GUFI).

### Claim 15 (depends on 11)

The method of claim 11, wherein said receiving comprises receiving the flight plan in the first data standard from a computerized flight-plan system.

### Claim 16 (depends on 11)

The method of claim 11, further comprising showing, by the control unit, the flight plan in one or both of the first data standard or the second data standard on a display of a user interface.

### Claim 17 (depends on 16)

The method of claim 16, further comprising showing, by the control unit, a route comparison on the display.

### Claim 18 (depends on 11)

The method of claim 11, further comprising operating the aircraft according to the flight plan in the second data standard.

### Claim 19

A system comprising:
an aircraft;
a user interface including a display and an input device; and
a control unit in communication with the user interface, wherein the control unit is configured to:
receive, from a computerized flight-plan system, a flight plan for the aircraft, wherein the flight plan is in a first data standard, wherein the first data standard is one of extensible markup language (XML), JavaScript Object Notation (JSON), Plain Text (TXT), or Portable Document Format (PDF),
convert the flight plan in the first data standard into the flight plan in a second data standard, wherein the second data standard differs from the first data standard, wherein the second data standard is Flight-and-Flow Information for Collaborative Environment (FF-ICE),
show the flight plan in one or both of the first data standard or the second data standard on the display,
show a route comparison on the display,
submit the flight plan in the second standard to an FF-ICE filing service, and
interpret a reply from the FF-ICE filing service,
wherein the aircraft is configured to be operated according to the flight plan in the second data standard.

### Claim 20 (depends on 19)

The system of claim 19, wherein the control unit is further configured to convert the flight plan in the first data standard into a flight information exchange model (FIXM) flight plan format by, at least in part, creating a globally unique flight identifier (GUFI).
