The operating question
Flight tests depend on aircraft, sites, people, permissions, and weather, so inconsistent status increases safety and compliance risk.

CITY OPERATIONS
Flight-test activities remain planned. Proposed coordination covers test goals, prerequisites, materials, and records, not currently available flight testing.
Flight tests depend on aircraft, sites, people, permissions, and weather, so inconsistent status increases safety and compliance risk.
The proposed approach considers checklists, plan versions, roles, archives, and issue review once eligible operators define test and permission requirements. Delivery arrangements remain unconfirmed.
System composition
Eligible entities would confirm aircraft, site, personnel, permission, weather, and safety requirements, with each condition recorded by status.
The proposed work would maintain plan versions for objectives, test points, time windows, roles, and changes without taking flight decisions or controlling aircraft.
Authorised materials, activity records, and issue feedback would be archived as agreed for responsible entities to review, not as airworthiness or performance conclusions.
Working approach
If discussions proceed, eligible entities identify the test objective, required permissions, and safety responsibilities before deciding whether further planning is appropriate.
Once responsibilities are clear, discuss condition lists, plan templates, information access, and record requirements for responsible parties to review.
Eligible entities must complete all permission, safety, and execution arrangements before any test. ZNAero would only undertake information coordination under a separate agreement.
Share the test objective, responsible entities, and available conditions. This is a planning discussion, not a request for flight testing.