An APU borescope inspection can look simple on a maintenance forecast: arrange access, bring in the inspection provider, review the images, close the work order. In practice, the way you coordinate APU borescope inspection often determines whether it is a controlled maintenance event or an avoidable extension of downtime. The inspection itself may take hours. Sorting out unclear scope, missing records, access issues, or a questionable finding can take much longer.
For a flight department, the goal is not merely to complete a required task. The goal is to get a useful technical answer, make a sound maintenance decision, and return the aircraft to service without surprises. That takes planning before the borescope ever goes into the APU.
Start With the Actual Inspection Requirement
The first question is not, “Who can perform the borescope?” It is, “What exactly is required?” The answer may come from the APU maintenance manual, an engine program requirement, a pre-purchase inspection scope, a trend-monitoring concern, an abnormal event, or a discrepancy found during another inspection.
Those are not interchangeable scopes. A scheduled inspection might require visual evaluation of specific internal sections at defined intervals. A pre-purchase review may call for broader documentation and a more conservative assessment of any finding. If the aircraft had an overtemperature event, abnormal start, oil consumption concern, or repeated fault message, the inspection should be tailored to that event rather than treated as a routine calendar item.
Before scheduling, confirm the APU model and serial number, current hours and cycles, applicable maintenance manual references, program requirements, and the reason for the inspection. Also determine whether the provider needs only images and observations or a formal report with measurements, annotated photos, and a serviceability statement.
That sounds basic, but vague wording such as “APU borescope as needed” is where scope creep starts. A clear inspection request gives everyone a working definition of complete.
Choose Timing That Protects the Schedule
A borescope inspection should rarely be scheduled as an isolated event if the aircraft is already coming down for related maintenance. When practical, coordinate it with a scheduled inspection, avionics downtime, interior work, an engine or APU service event, or a pre-purchase evaluation. Combining access-dependent work can reduce positioning, labor duplication, and days on the ground.
There is a trade-off. Bundling work is efficient when the schedule has room and the aircraft will already be opened up. It is less efficient when adding the inspection creates a critical-path risk before a fixed trip or delivery date. If the aircraft has an active concern, waiting for the next larger maintenance event can be the wrong call.
The honest answer is that timing depends on why the inspection is being done. A routine requirement can usually be planned. A suspected hot-section issue or abnormal operating event needs a faster decision. Do not let a calendar convenience override the maintenance reason.
Build Contingency Into the Downtime Window
The scheduled inspection time is not the whole story. A realistic plan includes room to review images, consult technical support if needed, obtain parts, and address discrepancies that may be found. Not every indication is a removal event, but some findings will require more than a quick signoff.
Ask the maintenance provider to identify the likely decision points before the aircraft arrives. For example: What happens if the inspector finds blade distress, liner damage, foreign object damage, or evidence of overheating? Who has authority to approve additional work? How quickly can replacement components or an exchange APU be sourced if the finding warrants removal?
A schedule that assumes every inspection will be clean is not a schedule. It is a hope.
Make Records Available Before the Aircraft Arrives
The inspection provider should not be trying to reconstruct the APU’s history while the aircraft is occupying a maintenance slot. Relevant records help the inspector understand what they are seeing and help the operator make an informed decision afterward.
Provide recent APU logbook entries, prior borescope reports and images, removal and installation history, trend data when available, fault history, oil servicing information, and records related to any abnormal event. If the APU is enrolled in a maintenance program, clarify the program administrator’s reporting and authorization requirements early.
Prior images are particularly valuable. A small indication can be hard to classify from one inspection alone. If comparable images show the same condition has remained stable over time, the maintenance decision may be different than if the condition is new or progressing.
Records also protect the operator from paying for guesswork. A qualified technician can inspect the hardware, but maintenance history provides the context that turns an image into a decision.
Confirm Access, Equipment, and Aircraft Condition
Not every borescope setup produces the same quality of inspection. Access points, required tooling, probe articulation, image capture capability, and lighting all matter. So does the technician’s familiarity with that APU model.
Confirm that the inspection provider has the proper equipment and current technical data for the specific unit. Ask how images will be captured, labeled, and delivered. Grainy photos without orientation, location, or explanation do not give a director of maintenance much to work with later.
Aircraft condition needs to be planned as well. The APU must be cool enough for safe access. The aircraft may need to be positioned in a specific location, connected to ground power, or made available without other work blocking access. If panels, insulation, or surrounding components need to be removed, establish whether that labor is included in the estimate.
This is where quotes often get muddy. A clean quote distinguishes between the base inspection, access and close-up labor, report preparation, travel if applicable, and any additional troubleshooting or corrective action. Nobody expects a provider to predict every discrepancy. Everyone should expect them to explain what is included before the invoice arrives.
Keep the Right People in the Decision Loop
A borescope inspection can involve the operator, maintenance facility, mobile borescope provider, APU program administrator, technical representative, broker, or prospective buyer. Too many voices can slow a decision. Too few can create authorization problems after the fact.
Set the communication path before work starts. Identify who receives the initial finding, who can authorize additional diagnostic work, who approves removal or replacement, and who needs the final report. If the aircraft is being evaluated for purchase, define whether findings are communicated first to the buyer’s representative, seller, escrow team, or all designated parties.
The best communication is factual and prompt. A useful finding report states what was inspected, what was observed, where it was observed, whether the condition is within published limits or requires further evaluation, and what the practical next step is. It should not bury the operator in vague language or force them to chase three people for a direct answer.
At Aviation Maintenance Professionals, that is the standard we work toward on coordinated inspections: clear scope before the aircraft arrives, straight communication while the work is underway, and a documented path forward if the inspection does not come back clean.
Review Findings Without Overreacting or Minimizing Them
A borescope image is evidence, not a verdict by itself. Discoloration, deposits, nicks, erosion, cracking, coating loss, or blade distress may have very different significance depending on location, extent, maintenance manual limits, operating history, and whether the condition is changing.
That is why a good inspection report should separate observation from recommendation. “Evidence of distress was observed” is not enough. The operator needs to know whether the condition is acceptable for continued service, requires monitoring, needs manufacturer or program review, or supports removal.
There is also a financial side to the decision. Removing an APU based on an unclear image can create unnecessary expense and downtime. Continuing to operate with a condition that exceeds limits can create a much larger problem later. The right answer is not automatically the cheapest one or the fastest one. It is the answer supported by the applicable data and clearly documented technical judgment.
Protect the Return-to-Service Plan
Once findings are reviewed, close the loop. Make sure the final report, images, work order entries, and any required program submissions are complete. If monitoring is recommended, put the next inspection or review point into the maintenance forecast with a specific trigger, not a note that gets lost in a logbook.
If removal is required, move immediately from diagnosis to logistics. Confirm unit availability, shipping, installation scope, operational checks, program approvals, and the realistic return-to-service date. The aircraft does not care whether the delay came from a finding, a missing approval, or a part that was never requested. It is still down.
A well-coordinated APU borescope inspection does more than satisfy a requirement. It gives the operator a clear picture of the unit’s condition and enough time to make the next decision without pressure, guesswork, or a surprise invoice.