Current Romania thermal-work route
Use the current EASA UAS framework and the Romanian Civil Aeronautical Authority (AACR) route for the actual thermal-inspection mission. Confirm the operating category, operator registration, pilot competency, geographical zones, site permission, data handling and whether operational authorisation is required. Request any current applicable charge from AACR or the named provider; do not reuse an old cost figure.
Romania thermal-project evidence brief
A thermal payload, a paid inspection brief and an aircraft model do not produce a universal category, approval or cost answer. Start with the actual asset, expected deliverable, people and site context, exact equipment and ground alternative. Then use the current Romanian and project-specific routes for the proposed operation.
What should a Romania thermal-inspection team establish before proposing drone work?

Why should a thermal-inspection proposal separate project evidence from an approval or cost claim?
Thermal imagery can be part of a larger inspection process, but it does not decide a property's condition or the route for a proposed activity. The responsible team needs the exact system, asset context, client evidence standard and current project route. This preserves a useful decision path without treating a historic course, category or price example as a current answer.
How should a team turn the review into an action plan?
Related Reboot Hub paths
Frequently asked questions
Can this page decide a Romania thermal-drone approval or cost?
No. Confirm current requirements through the relevant route for the actual system, site, project and proposed activity.
Does a thermal payload establish what an inspection will prove?
No. The client question, system evidence, site context and responsible review determine the scope of the deliverable.
Why retain a ground-inspection alternative?
It preserves the client evidence path when the available equipment evidence or current route does not support the aerial element.
What should be included in the project file?
Keep the inspection brief, exact system record, site responses, current route response, data-handoff plan and fallback together.
When should the project evidence be reviewed again?
Review it when the asset, system, site, client requirement, project scope or dates change.
Keep exploring
Further reading
From ה-Reboot Hub Chronicle
From מדריכי מזל"ט

































































