Skip to content

Inspector.aero · Technology by ADD Aviation

Every walkaround.
Clearly documented.

For aviation consultants and technical teams: document aircraft and engines in the field with the app, and review projects, photographs and findings through the web platform.

Aircraft categories
Engine categories

An aviation structure for your walkaround.

Actual aircraft and engine categories in Inspector. See the capture workflow

Inspector.aero · By ADD Aviation

One inspection.
Five connected capabilities.

Inspector helps aviation consultants and technical teams document aircraft and engines, explain observations and review findings alongside their evidence. The mobile app supports work in the field. The web platform extends the review to the desktop, within the context of each project.

Inspector Capture

Capture the detail.
Keep the context.

During a walkaround, a photograph needs more than a clear image: it needs a place where the team can find it. Inspector Capture organizes the inspection journey by categories and subcategories, helping you document an aircraft or engine with a clear reference to its inspection location.

The result: a gallery that keeps the project, the inspection area and each photograph connected.

In the field · Mobile app

Document from the area you are inspecting.

Open the project, choose the category and enter the relevant subcategory before working with its images. The camera workflow described for Inspector starts from that inspection location; the gallery lets you return to a photograph and continue into Mark Up when a detail needs an explanation. This structure brings context to capture and supports later review.

At the desk · Web platform

Review coverage through a familiar structure.

On the web, browse the aircraft or engine categories and consult their photographs. The counts and observations visible in the project help orient the review and identify which area to examine next. The office team can locate evidence by its inspection context, without relying solely on a file name.

Locate

Identify the project, category and subcategory that correspond to the inspection area.

Document

Record the image within the inspection workflow and retain its location reference.

Retrieve

Return to the gallery to examine a detail, add an explanation or support technical review.

Organization starts with the location selected by the inspector. Aircraft and engine photographs retain their respective inspection paths and galleries.

Inspector Mark Up

Show where to look.
Explain what you observed.

A photograph shows a surface; an annotation directs attention to the relevant detail. Inspector Mark Up provides drawing and shape tools over the image to make an observation clearer and support the technical conversation between the inspector and the reviewer.

The result: a visual reference that helps people understand the observation in context.

In the field · Mobile app

Annotate the inspection photograph.

Open a gallery image and enter Mark Up. The tools let you choose how to identify the detail and adjust the color and line width. The mark provides a visual reference: the technical description should explain what was observed, where it is located and what requires review.

At the desk · Web platform

Interpret the detail within the project.

Web review lets you consult photographs and existing annotation examples in the project. The images here show the same engine area in an original photograph and in a retained annotated image. That visual context helps the team discuss an observation while keeping a reference to the evidence behind it.

Inspector Mark Up

Inside Mark Up.

The sequence moves through the viewer, editor, tools, colors and line widths over the same photograph of fan blades.

  • Drawing
  • Shapes
  • Color
  • Line width

A sequence of five actual screens over the same photograph: viewer, editor, tools, colors and line widths.

Show or hide the tools sequenceFive mobile screens show the same fan-blade photograph in the viewer, the editor, the tool palette, the color palette and the line width selector.Mark Up displays a photograph of fan blades, with a vertical palette for drawing, a text bubble, arrow, line, rectangle and circle, above the editor toolbar.

A still view of the editor is shown when reduced motion is enabled.

An annotation supports communication. Damage assessment and the appropriate action still depend on technical judgment and the applicable documentation.

Inspector Crew

The work in the field.
The perspective of the team.

An inspection may involve a consultant beside the asset, a project lead in the office and a technical team reviewing progress. Inspector Crew organizes that participation around projects and teams, with a working context that authorized people can consult.

The result: a common reference for coordinating inspection documentation and review.

In the field · Mobile app

Choose the team and continue with the right project.

In Change Team, Current Team shows the active team. Choose an available team or your Personal Hub, then return to Projects to consult its projects. This workflow helps you continue with the right client and asset within the same account. Before documenting, confirm the team, project and inspection area.

At the desk · Web platform

Review several clients from My Projects.

In My Projects, expand the client’s Team group and open its aircraft or engine project. To review another client, return to the list and expand the other group; several groups can remain open. This helps you locate the inspection for each assignment and review its photographs and findings within your account’s access.

Field work

The inspector documents the asset and contributes the observation with its evidence and location.

Coordination

The project lead reviews the context and organizes the questions that need follow-up.

Technical review

The authorized team consults project information and works through findings that require attention.

Crew project management focuses on the inspection context: team, asset, photographs and findings. The OIL develops technical follow-up within Inspector Findings.

Inspector Findings

A finding.
Its evidence and follow-up.

Inspector Findings brings open items together in the OIL, Open Items List. The inspection location, discrepancy and reference photograph allow each observation to be reviewed as part of the project. The technical conversation can draw on an organized record shared by the authorized team.

The result: a clear basis for reviewing open items, preparing deliverables and organizing technical follow-up.

In the field · Mobile app

Consult the OIL beside the asset.

Open OIL Dashboard from the project. When findings are present, each row shows the location and a thumbnail. Open the row in OIL Tracking to review the photograph, discrepancy and existing entries. The Options menu on an open finding can show a Close Item control.

At the desk · Web platform

Review items with a project perspective.

In Open Items List, locate the finding by its inspection location and read the discrepancy beside its reference photograph. These details can also be consulted in OIL Tracking on the phone. At a desk, the project lead can prepare the technical review, organize questions for the team and identify documentation that needs follow-up.

What was observed

A clear description of the discrepancy or point that requires review.

Where, and with what evidence

The inspection location and image that help identify the detail.

What comes next

Recorded comments and statuses to support follow-up by authorized people.

A comment or status change records an action within the project. Technical or contractual acceptance requires the appropriate review and authorization.

Inspector Hub

Evidence keeps
its place in the project.

Inspector Hub supports continuity by bringing project context and its images together within Inspector. The app serves work beside the asset; the web platform provides a place to consult photographs, categories and findings from the desktop.

The result: an information structure that lets people return to evidence and understand the inspection it belongs to.

In the field · Mobile app

Return to the project when you need the context.

Return to the team and project to consult a photograph or review a finding at its inspection location. The Project menu brings together Download from the cloud and Remove from device options for project availability on the phone. Galleries retain the inspection-area reference when you need to revisit an observation beside the asset.

See how teams and projects are accessed on the phone

At the desk · Web platform

Examine evidence with more room for review.

The web viewer lets you open a photograph, zoom in and reset the view to examine a detail. The image remains part of the project review, preserving a reference to the inspection structure and related observations. The desktop provides a review surface that complements mobile capture.

Inspector’s infrastructure serves this workflow: organizing information by project and enabling authorized team members to consult it. A shared structure supports capture, explanation and review.

The experience behind Inspector

Real aviation work.
Technology developed by ADD Aviation.

ADD Aviation develops its own technology and delivers specialist technical services to help clients understand, document and manage their assets. Inspector grows from that connection between field work and tool development: observing how inspections are performed, understanding what the next participant needs to know and organizing information so it can be useful.

Aviation Intelligence

A photograph gains value when it is connected to the asset, the inspection area, the observation and professional judgment. Connecting information with experience is the intelligence that guides ADD.

Infrastructure that supports the work

The app, web access and project structure serve a shared purpose: helping evidence be documented, located and reviewed in the right context. Technology is explained through the work it enables.

Continuity with the client

Understanding the scope of an inspection and how the client reviews its results helps prepare a useful workflow. The conversation starts with the asset, the people involved and the information they need to make decisions.

People working with aviation assets

One tool.
Different responsibilities.

The consultant needs to document clearly; the person directing or commissioning the inspection needs to understand and review the result. Inspector presents evidence in a context that helps connect those responsibilities.

Independent consultants and inspectors

Document aircraft and engines within an organized inspection journey. Switch teams when participating in projects for different clients and retain a visual explanation of observations that need review.

Consultancies and project leads

Coordinate the team's documentation and review projects from the web. Use categories, photographs and the OIL to prepare technical conversations and follow up on work that needs attention.

Lessors, owners and asset managers

Consult evidence and findings for projects you can access. Inspection context helps you ask questions, understand observations and prepare the review with your technical team.

Operator and MRO technical teams

Organize visual evidence of aircraft and engines for team review. Define the project scope around the asset, the intervention and the people who need to consult the results.

Product direction · Future capability

A professional community
with evidence of its work.

Inspector's direction is to extend the tool's value to consultants around the world. In the future, ADD Aviation aims to explore an environment where professionals can present their services and those commissioning them can find references and evaluations grounded in documented work.

A service provider directory and inspector evaluations are part of this vision. They are not currently available and have no announced launch date.

Questions about working with Inspector

The context
before you begin.

What is Inspector.aero?

It is an ADD Aviation platform for documenting aviation inspections through organized photographs, visual annotations and findings linked to their evidence. It combines a mobile app for field work with a web platform for reviewing project context.

What do I do on the phone and on the web?

The app lets you browse projects and inspection areas, work with photographs, open Mark Up and consult the OIL. On the desktop, you review teams, projects, categories, images and findings. Each environment serves part of the workflow; available actions depend on access and the project.

Can I work with different clients?

Yes. An account can provide access to projects across different teams. On the phone, Change Team selects the active team. On the web, My Projects provides expandable Team groups. Each person works within the projects they can access.

Does Inspector support aircraft and engines?

The screenshots on this page show projects with aircraft and engine categories, including engine component galleries. Each workflow retains the organization of its respective project.

How do field and office teams work together?

In the field, the inspector documents the asset, organizes photographs and uses Mark Up to explain details. On the web, the project lead consults categories, images and the OIL to prepare the review and follow the team’s observations. Both workflows are organized around the inspection project.

What does OIL mean?

OIL means Open Items List: the inspection's list of open items. In Inspector, it links observations to their location and evidence. OIL Dashboard presents the list on mobile; OIL Tracking lets you consult an item's details.

Does an annotation or status replace technical assessment?

Mark Up supports visual explanation and the OIL documents follow-up. Assessing the finding, its acceptability and the appropriate action depends on the authorized professional, applicable documentation and agreed project scope.

What should I confirm before working offline?

Confirm which information will be available on the device, which operations can be performed and how changes are transferred when connectivity returns. Check these conditions for the version and workflow in use before relying on them during an inspection.

How do I prepare a report or a findings handover?

Define the handover scope, review the OIL and check that each observation has sufficient location, description and evidence. A structured list supports the findings review and helps explain to the recipient what needs attention and why.

Can I already hire or evaluate inspectors on the platform?

No. A service directory and professional evaluations belong to the product's future vision. The current presentation focuses on inspection documentation and review capabilities.

Get started

Continue with Inspector.aero.

Open your projects on the web or view the app download for field work. To prepare an inspection with your team, define the asset, the scope and the people who will review the evidence.

Mobile app · App interface in English. See the App Store for compatibility.