Airspace Verification Review

A good airspace review should be reproducible.

Another reviewer should be able to see which operation you analyzed, which current source you checked, what the source established, what permission remains separate, and what must be rechecked before flight.

This lesson uses a fictional mission and supplied training records. Do not submit a live LAANC request or treat this classroom review as flight authorization.

The proposed mission

purpose: roof-imaging exercise
site: fictional school campus
operating framework: Part 107 training scenario
requested altitude: 120 ft AGL
requested time: 10:30–10:50 a.m.
airspace: controlled in supplied training record
site permission: documented
FAA authorization: supplied training example
weather check: not yet complete
TFR/current restriction check: supplied record is from yesterday

The packet looks organized.

It is still not ready.

Why?

The time-sensitive restriction evidence is stale for a real operation and the weather gate is unresolved.

Verify exact match, not vague similarity

Authorization evidence has to match the proposed mission conditions.

Check:

• location;
• altitude;
• time/date;
• operator/operating framework where relevant;
• conditions or provisions in the authorization.

A document for “the school area sometime Friday” is not the same thing as evidence for the exact planned operation.

For classroom work, compare the supplied fields one by one.

Separate four evidence layers

Build your review around four folders or sections.

1. Airspace classification and current restrictions

Use current FAA or supplied training evidence to identify the airspace and time-sensitive restrictions.

2. FAA authorization

If the reviewed framework requires authorization, record whether the supplied mission has it and whether the conditions match.

3. Site authority

Record who controls the launch/recovery site and whether the school/property layer is approved.

4. Operational readiness

Weather, crew, aircraft, route, bystanders, obstacles, and recovery planning belong here.

Do not let a green result in one folder leak into another.

Worked defect: wrong altitude

A fictional authorization example covers operation at or below 100 ft AGL for the requested location and time.

The mission file is configured for 120 ft AGL.

The mission is not compliant with the supplied authorization example.

The correct classroom disposition is:

Revise the mission or obtain the appropriate qualified review/authorization.

Do not round 120 down to “about 100.”

Aviation planning depends on exact conditions.

Worked defect: correct authorization, stale restriction check

Another packet has:

• matching altitude;
• matching location;
• matching time;
• site permission;
• FAA authorization;
• TFR/restriction screenshot captured 48 hours earlier.

For a real operation, that restriction evidence is too old to establish current status.

The right conclusion is not “denied.”

It is:

Current verification still required.

That distinction matters. An unresolved gate is not the same thing as proof of a prohibited operation.

Current FAA sources should remain visible

Your review should identify the source category, not only paste a screenshot.

Examples of current FAA entry points include:

• Where Can I Fly?
• LAANC
• FAA pages for the applicable recreational or Part 107 operating framework.

In a real mission, the qualified operator would use the current approved tools and procedures available at that time.

Build the verification record

Use this structure:

Then add a timestamp field for anything that can change.

Avoid “green map syndrome”

A common planning failure is assuming that one map display is the whole answer.

A map can help answer:

• where the site sits;
• what airspace layer or facility-map data applies;
• whether a restriction is shown by that service at that moment.

It does not establish every operating rule, property permission, weather condition, aircraft limit, or crew-readiness factor.

A map is evidence. It is not the mission commander.

Reviewer challenge

Exchange fictional mission packets with another student.

The reviewer should try to find:

• one mismatch;
• one missing timestamp;
• one authority that was confused with another authority;
• one condition that needs a current recheck;
• one claim stronger than the evidence supports.

Then repair the packet.

Week 10 conclusion

Airspace planning is not about memorizing where colored zones appear.

It is about creating an audit trail from exact mission → current source → required authorization → issued conditions → independent site/safety gates → recheck before operation.

If another person cannot reproduce that chain, the mission is not ready for serious review.