Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions research/B1.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,3 +37,10 @@ DAL137-PIKIL/1405 M082F370

- Recipient authority could be the FIR code, e.g. EGGX or KZOA, or it could be a SITA(?) address, e.g. PIKCLXS
- Remarks are not required but are possible, there are examples in [Appendix B of this document](https://www.notams.faa.gov/downloads/ShanwickOceanicClx.pdf)

EGGX = ATC Oceanic Center
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

EGGX description is inaccurate — use the precise ICAO term.

"ATC Oceanic Center" is not the standard designation. EGGX is the FIR identifier for the Shanwick Oceanic Control Area (OCA) and Flight Information Region (FIR). This is consistent with line 38 of the document, which already identifies EGGX as a "FIR code". Recommend updating to something like: EGGX = Shanwick Oceanic FIR / OCA (ICAO FIR identifier).

✏️ Suggested fix
-EGGX = ATC Oceanic Center
+EGGX = Shanwick Oceanic FIR / OCA (ICAO FIR identifier)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@research/B1.md` at line 41, The EGGX description is too generic; change the
value for EGGX to the precise ICAO designation by replacing "ATC Oceanic Center"
with a clear identifier such as "Shanwick Oceanic FIR / OCA (ICAO FIR
identifier)" so the document uses the correct FIR/OCA terminology for the EGGX
code.

AFR088 = Flight Number or Callsign
BALIX = Oceanic Route Entry (Way)Point
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

BALIX definition should use the standard ICAO term "Oceanic Entry Point (OEP)".

The Oceanic Entry Point is generally a "named" waypoint, on or close to the FIR boundary where the aircraft enters an oceanic control area — standardly abbreviated OEP. The current wording "Oceanic Route Entry (Way)Point" is an informal paraphrase that diverges from the OEP terminology already used in line 35 of the same document (\<Oceanic entry waypoint\>).

✏️ Suggested fix
-BALIX = Oceanic Route Entry (Way)Point
+BALIX = Oceanic Entry Point (OEP)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
BALIX = Oceanic Route Entry (Way)Point
BALIX = Oceanic Entry Point (OEP)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@research/B1.md` at line 43, Replace the informal definition of BALIX with the
standard ICAO term by changing "BALIX = Oceanic Route Entry (Way)Point" to use
"Oceanic Entry Point (OEP)" so the line reads something like "BALIX = Oceanic
Entry Point (OEP)"; ensure the abbreviation OEP is included and consistent with
the earlier `<Oceanic entry waypoint>` usage in the document.

1754 = HHMM ETA UTC over Oceanic Route Entry (Way)Point
M083 = Mach Number (083=0.83)
F360 = Flight Level (360=36000ft)