AIRSPACE ORACLESTRATEGIC AIRSPACE CONSULTING

Airspace strategy · Planning · Instruction

Practical airspace planning.

Clear next steps.

Operational insight translated into practical concepts, coordinated planning products, and scenario-based training.

Start a ProjectExplore Services

NO SLACK IN THE STACK.
From the box to the pen.

Explore this pageServicesInsightsTALASExperienceContact
OPERATIONAL PERSPECTIVECIVIL–MILITARY COORDINATIONSCENARIO-BASED INSTRUCTIONExplore ↓

01 / Expertise

Practical support

From a complex problem
to a usable planning product.

Support for aerospace teams, training organizations, and program leaders who need clear assumptions, structured options, and practical next steps.

01 / REVIEW

Airspace Concept Review

For teams assessing an early-stage operation or planning concept.

  • Requirements and assumptions discussion
  • Annotated concept diagram
  • Constraints and coordination-gap register
  • Findings and next-step brief

Advisory review—not approval or authorization.

Build a brief ↗
02 / DEVELOP

Planning & Integration Support

For teams translating an idea into a coordinated planning approach.

  • Operational concept outline
  • Airspace visualization
  • Stakeholder and coordination matrix
  • Planning checklist and decision brief

Geographic and technical scope agreed before work begins.

Build a brief ↗
03 / TEACH

Training & Workshops

For universities, industry teams, and operational planners.

  • Agreed learning objectives
  • Instructor-led seminar or workshop
  • Scenario exercise and participant materials
  • Facilitated after-action discussion

Audience, format, and objectives defined together.

Build a brief ↗

A clear scope. A practical outcome.

01 / Discuss

Define the problem, audience, timeline, and fit.

02 / Scope

Agree deliverables, exclusions, assumptions, and fees.

03 / Develop

Build the agreed product with review points.

04 / Review

Explain findings, limitations, and revisions.

05 / Close out

Deliver final materials and confirm next steps.

02 / Perspectives

Insights from the Field

Getting the operational fundamentals right.

Practical perspectives on the gap between introducing a capability and making it work—through airspace planning, coordination, training, and sustainment.

PLAN / COORDINATE / EXECUTE
Execution & Ground Truth

Airspace Is More Than a Control Measure

A clear overlay is only the beginning. Explore the responsibilities, coordination points, and fallback decisions that connect an airspace plan to execution.

CAPABILITY / PEOPLE / SUPPORT
Capability Integration

Demonstration Is Not Integration

A successful demonstration answers a narrow question. Explore what still needs to be understood about people, procedures, coordination, and sustainment.

CIVIL / SHARED / MILITARY
Civil-Military Integration

Shared Airspace Starts with Shared Understanding

Different organizations bring different responsibilities to the same airspace. Start with shared assumptions, understandable requests, and clear coordination.

DEMAND / SUPPLY / ENDURANCE
Operational Sustainment

Before We Add Another System, How Will We Power It?

Power belongs in the planning conversation—not at the end of it. Ask how loads, charging, fuel, maintenance, and backup affect the operating concept.

CONTROL / COORDINATE / PLAN
Workforce Development

From ATC to Airspace: Bridging the Planning Gap

Build on control experience while expanding the planning picture. Connect airspace users, coordination responsibilities, timing, and decision-making.

REQUIREMENTS / LAYERS / DECISIONS
Doctrinal Architecture

Why I Developed TALAS: The Problem Before the Framework

Begin with the planning problem, not the acronym. Explore the questions behind TALAS without treating a conceptual framework as validated doctrine.

03 / Framework Spotlight

TALAS

Tactical Airspace Layering and Allocation System

An author-developed framework proposed by Giac T. Ly for examining how airspace can be organized and allocated around operational requirements.

Presented as a concept—not adopted doctrine, independently validated performance, regulatory acceptance, or operational approval.

Build a briefing request

Discussion outline—not a TALAS technical specification.

Define the operating problemUsers, activities, constraints, and assumptions.
Examine allocation optionsCompeting requirements and coordination dependencies.
Identify decisions and limitsResponsibilities, unresolved questions, and validation needs.

Experience & Perspective

Giac T. Ly

Founder / Airspace Oracle

The Warpig spirit.

Practical thinking. Direct communication.
No slack in the stack.

04 / About

Experience & Perspective

Connecting operational requirements with practical airspace planning.

My perspective comes from military aviation, air traffic control, and operational airspace management, including service as Aviation Division Chief at the National Training Center, Fort Irwin; participation in Project Convergence; and years of civil-military airspace integration in Korea.

My work focuses on connecting operational requirements with practical airspace planning, coordination, and training. My interests include preparing airspace personnel for responsibilities beyond the control facility, integrating emerging capabilities, and examining the foundational requirements that make technology usable in the field.

My career experience includes work with Anduril beginning with Project Convergence at Fort Irwin/NTC, and experimental capability projects in Korea involving the Future Capabilities Directorate and T2COM. Current-project details and nonpublic technical information are intentionally excluded.

  • Aviation Division Chief, National Training Center (NTC), Fort Irwin
  • Joint & Emerging Technology Airspace Integration (Project Convergence)
  • Host-Nation Civil-Military Airspace Coordination & Integration in Korea
  • Advanced Air Traffic Control (15Q) & Warrant Officer Airspace Leadership
  • Developed TALAS; wrote on power-generation and sustainment issues.
  • Built training bridging 15Q air traffic control experience and intermediate airspace skills.
The story behind the Oracle

Born in Saigon, Giac left Vietnam by boat in 1988 (MC138) and resettled in the United States in 1990. He joined the Army in 1995, serving as an 82nd Airborne paratrooper and combat engineer before transitioning to air traffic control and warrant officer service. His journey informs a practical, service-oriented approach to complex challenges.

University Outreach

Guest instruction and community outreach with Hanseo University, including a lecture comparing civil and military airspace systems.

Read Chungnam Ilbo coverage ↗

Media coverage of the founder’s educational outreach at Hanseo University. This reference does not imply university or publisher endorsement of Airspace Oracle.

05 / Project Brief

Build a clear project brief.

Organize a non-sensitive project summary, review the briefing preview, and prepare an inquiry. This browser-based workspace does not submit information or create an agreed scope.

0 / 6Core briefing fields completed

Project inputs

Use a fictional or high-level summary. Do not enter classified, controlled, export-controlled, proprietary, or personal-sensitive information.

Without local saving, entries stay in page memory only. Nothing is submitted from this brief.

Live briefing preview

Counts reflect completed fields—not feasibility, safety, or approval.

Scope, fees, availability, and information handling require separate agreement. No automated quote or approval is generated.




06 / Before We Begin
Before we begin
Clear expectations
from the first conversation.
Start with the question you need answered and the product your team needs to use.
Can you secure an airspace approval?
No approval is promised. Advisory work can organize requirements and coordination questions; decisions remain with the relevant authorities.
How are projects priced?
A written proposal defines deliverables, exclusions, schedule, review points, and fees before work starts.
Can you provide a seminar or guest lecture?
Describe the audience, subject, format, and timing. Availability and suitability are confirmed before scheduling.
May I send sensitive project material?
Not through this website or ordinary inquiry email. Begin with a non-sensitive summary and agree any additional arrangements separately.


07 / Contact
What decision does
your team need to make?
Share the challenge, intended audience, and desired outcome. A short, non-sensitive summary is enough to begin.
contact@airspaceoracle.com
South Korea · Korea Standard Time (UTC+9)
Do not submit classified, controlled, export-controlled, proprietary, or otherwise sensitive information.
An inquiry does not establish a consulting relationship or guarantee availability.
Read the inquiry privacy notice before submitting.
Opens a draft in your mail app. Review and send it yourself; this website does not send your inquiry.



Airspace Oracle / Capabilities
Giac T. Ly · Founder-led strategic airspace consulting
Core capabilities
Relevant experience
Military air traffic control, airspace planning, civil–military coordination in South Korea, and operational instruction.
Approach
Discuss → Scope → Develop → Review → Close out
Independent private initiative. Career references describe founder experience, not company past performance. No government, military, university, or industry endorsement is implied. Engagements are subject to applicable requirements and a separate written agreement.
contact@airspaceoracle.com · airspaceoracle.com
South Korea · UTC+9
Inquiry privacy notice
The contact form prepares an email draft locally and opens your configured mail app. No form backend receives the inquiry. You must review and send the email yourself. Hosting and email providers may process technical information under their policies.
The project brief processes entries in your browser. Optional local saving is off by default. If enabled, briefing data is stored on that browser profile—not in an authenticated private account. Clear brief data removes that saved brief, not emails you sent or copies you exported.
Prepare inquiry fills the form only. Prepare Email Draft opens your mail app without sending automatically. Copy, print, and download create copies under your control.
Contact contact@airspaceoracle.com about access, correction, or deletion requests. Applicable obligations and provider capabilities may affect a request. Do not include sensitive information.
No third-party analytics or advertising scripts are intentionally added to this HTML.
Website terms
Content describes proposed advisory services and educational examples. It is not flight authorization, legal advice, safety assurance, or a substitute for applicable requirements and authority coordination.
Samples are illustrative. TALAS is an author-developed concept, not adopted doctrine or an independently validated standard.
Preparing an inquiry or completing a brief does not establish a client relationship or create approval. Deliverables, fees, confidentiality, intellectual property, and engagement terms require a separate agreement.
Original materials are attributed to Giac T. Ly unless otherwise indicated. No ownership of third-party marks or underlying ideas is asserted.
Private engagements
Any proposed engagement is subject to applicable ethics requirements, conflict review, required approvals, availability, and a separate written agreement. Website disclosures do not establish that an activity is permitted or approved.
Do not submit nonpublic government information or confidential third-party material. Public descriptions do not grant rights to use or redistribute government or third-party materials.
Airspace Oracle / Introduction
Use the player controls to start the introduction with sound.
Independence and Non-Endorsement
Airspace Oracle is an independent private initiative, separate from the founder’s federal employment and official duties. References to government service, organizations, and projects describe the founder’s professional experience—not Airspace Oracle’s clients, partnerships, or company past performance. No government, military, university, or industry endorsement is implied.
Engagement conditions
Private engagements are subject to applicable ethics requirements, any required approvals, availability, and a separate written agreement. Do not submit nonpublic government information or confidential third-party material.
These disclosures do not represent an ethics determination or authorization to undertake a particular activity.
Media references
External reporting is provided as context for the founder’s experience. References to educational events do not imply a commercial engagement or endorsement by the institution or publisher.
Scope and authority
Services are advisory and educational. No flight authorization, regulatory approval, engineering certification, procurement status, or independently validated performance is claimed. TALAS is presented conceptually, not as adopted doctrine.
Execution & Ground Truth / Planning perspective
Airspace Is More Than a Control Measure
A clear overlay is only the beginning. Explore the responsibilities, coordination points, and fallback decisions that connect an airspace plan to execution.
Core question
What should planners understand about connecting airspace plans to real-time execution?
The planning problem
A diagram can show where activity is intended to occur without explaining who makes a decision when the situation changes. This perspective asks planners to connect geometry with responsibilities, timing, and communication rather than treating the graphic as the finished product.
An illustrative scenario
A fictional training event includes several airspace users. A weather change affects the proposed sequence. Instead of simply redrawing a boundary, the team works through who needs to be informed, what must be reassessed, and who can authorize the next step.
Questions to bring to the table
Practical takeaway
Ask for a coordination and decision picture alongside the geometry. A useful planning product should make responsibilities and open questions visible.
Editorial planning discussion for review. Scenario is fictional, not a report of a specific operation. This is not doctrine, operational authorization, engineering design, or a claim of validated performance. Any use must follow applicable requirements and responsible authorities.
Capability Integration / Planning perspective
Demonstration Is Not Integration
A successful demonstration answers a narrow question. Explore what still needs to be understood about people, procedures, coordination, and sustainment.
Core question
What questions should an organization ask before treating a demonstrated capability as operationally integrated?
The planning problem
A demonstration can be useful evidence without answering every question about routine use. The planning challenge is to identify what the event actually tested, what support it depended on, and which assumptions remain open.
An illustrative scenario
A fictional team sees a capability perform during a short, well-supported event. Before extending the operating period, it lists the specialist support, connectivity, power, and coordination arrangements that made the demonstration possible.
Questions to bring to the table
Practical takeaway
Separate demonstration results from integration assumptions. A short evidence-and-dependencies register is a practical next discussion product.
Editorial planning discussion for review. Scenario is fictional, not a report of a specific operation. This is not doctrine, operational authorization, engineering design, or a claim of validated performance. Any use must follow applicable requirements and responsible authorities.
Civil-Military Integration / Planning perspective
Shared Airspace Starts with Shared Understanding
Different organizations bring different responsibilities to the same airspace. Start with shared assumptions, understandable requests, and clear coordination.
Core question
How do planners establish coordination across organizations with fundamentally different responsibilities?
The planning problem
A request that is clear to one organization may be incomplete or ambiguous to another. A useful starting point is to explain the proposed activity in terms that each stakeholder can assess, while leaving approval decisions with the responsible authorities.
An illustrative scenario
A fictional training organizer proposes activity near another airspace user. The teams compare time windows, requested geometry, points of contact, and how they will communicate a change before finalizing a request.
Questions to bring to the table
Practical takeaway
Shared understanding does not require identical missions. It requires a request that others can interpret and a coordination process they can follow.
Editorial planning discussion for review. Scenario is fictional, not a report of a specific operation. This is not doctrine, operational authorization, engineering design, or a claim of validated performance. Any use must follow applicable requirements and responsible authorities.
Operational Sustainment / Planning perspective
Before We Add Another System, How Will We Power It?
Power belongs in the planning conversation—not at the end of it. Ask how loads, charging, fuel, maintenance, and backup affect the operating concept.
Core question
What power and sustainment questions belong in capability planning from the beginning?
The planning problem
The operating concept should explain how equipment remains supported for the intended activity. This is an operational planning discussion: identify loads and dependencies, record assumptions, and ask qualified specialists to validate the technical solution.
An illustrative scenario
A fictional team plans a full-day activity after a short demonstration. It discovers that charging, backup, transport, and responsibility for replenishment were not included in the original schedule. Those become explicit planning questions rather than assumed support.
Questions to bring to the table
Practical takeaway
Make power and sustainment dependencies visible early. Keep engineering design, equipment sizing, installation, and safety validation with appropriately qualified specialists.
Editorial planning discussion for review. Scenario is fictional, not a report of a specific operation. This is not doctrine, operational authorization, engineering design, or a claim of validated performance. Any use must follow applicable requirements and responsible authorities.
Workforce Development / Planning perspective
From ATC to Airspace: Bridging the Planning Gap
Build on control experience while expanding the planning picture. Connect airspace users, coordination responsibilities, timing, and decision-making.
Core question
What additional knowledge prepares an ATC professional for brigade, division, and field-army responsibilities?
The planning problem
This perspective builds on the training gap identified in my work: moving from an ATC background toward intermediate airspace planning. The aim is not to diminish control experience, but to connect it with a wider set of users, responsibilities, and planning decisions.
An illustrative scenario
In a fictional workshop, participants receive a simple activity description and sketch the airspace users, information needs, decision owners, and coordination sequence. The exercise emphasizes explaining assumptions rather than reproducing a particular template.
Questions to bring to the table
Practical takeaway
Teach the transition explicitly: explain the broader problem, practice a coordination task, and review the reasoning behind the proposed plan.
Editorial planning discussion for review. Scenario is fictional, not a report of a specific operation. This is not doctrine, operational authorization, engineering design, or a claim of validated performance. Any use must follow applicable requirements and responsible authorities.
Doctrinal Architecture / Planning perspective
Why I Developed TALAS: The Problem Before the Framework
Begin with the planning problem, not the acronym. Explore the questions behind TALAS without treating a conceptual framework as validated doctrine.
Core question
What operational problem motivated the concept, and what can be understood without exposing sensitive details?
The planning problem
TALAS is presented here as an author-developed conceptual framework. The starting point is how to make competing airspace requirements, allocation options, and coordination responsibilities easier to understand. A public explanation should distinguish those questions from claims of technical or operational maturity.
An illustrative scenario
A fictional planning exercise introduces competing activities with overlapping time windows. Participants compare allocation options and explain the assumptions, decision responsibilities, and unresolved questions behind each option.
Questions to bring to the table
Practical takeaway
Explain the problem before promoting the framework. TALAS is not presented as adopted doctrine, independently validated performance, or operational approval.
Editorial planning discussion for review. Scenario is fictional, not a report of a specific operation. This is not doctrine, operational authorization, engineering design, or a claim of validated performance. Any use must follow applicable requirements and responsible authorities.