Thermal inspection for solar farms · SoCal
Find every failed string before it costs you a season.
Autonomous VTOL thermal inspection designed to cover an entire solar farm in one flight, with every fault pinned to its exact module.
Become a design partnerNo-cost inspections this winter for a small number of Southern California sites.
01 / The problem
Equipment faults cost the average U.S. solar site about 5% of its output.
That share has doubled in five years. Sites that are inspected more often lose less.
2019, 2023: Raptor Maps via PV Tech. 2021, 2025: Raptor Maps, 2026 Global Solar Report, via PV Tech (now.solar).
Figures come from different editions of the Raptor Maps report.
Source: Raptor Maps, 2026 Global Solar Report, via PV Tech (now.solar)
5%
Average production lost to equipment faults in 2025: 5.08%, across 373 GW of U.S. utility-scale and C&I solar. Up from 2.36% in 2021.
Source: Raptor Maps, 2026 Global Solar Report, via PV Tech (now.solar)
7% / 3%
Average power loss at sites inspected once a year, compared with sites inspected five times a year.
Source: Raptor Maps, 2026 Global Solar Report, via PV Tech (now.solar)
$5,070/MW
Annual revenue a U.S. site at the 2025 average loss rate could be losing, per MW.
Source: pv magazine, 25 February 2026
02 / How it works
Four steps, from site boundary to work orders.
Every flight will be flown by an FAA Part 107-certified remote pilot.
-
01
Plan
We take your site boundary and array layout, agree access with your site team, and schedule the flight for a window with enough irradiance for reliable thermal readings.
You provide: site boundary, layout, an on-site contact
-
02
Fly
The aircraft takes off vertically from a small clear area and flies a pre-planned route over the arrays, capturing thermal and RGB imagery while irradiance is logged. An FAA Part 107-certified remote pilot will be on site for every flight.
On site: one remote pilot, one small takeoff area
-
03
Report
We process the imagery into a report that places each fault on its module, classifies its severity, and attaches the frames behind it.
You receive: PDF, CSV and KML · see the sample
-
04
Fix
Your technicians go straight to the flagged modules, strings and combiners instead of walking rows. A follow-up flight can confirm the repairs.
Result: a prioritized fault list your crew can work from
03 / What you get
A fault list your technicians can work from, module by module.
Each inspection produces one report, in the formats your team already uses.
| Module-level geolocated faults | Each fault located to block, row, string and module, with coordinates. |
|---|---|
| Severity | Each fault classified by severity, so crews fix the largest production and safety risks first. |
| Thermal + RGB frames | The radiometric thermal frame and the matching RGB frame behind every finding. |
| Irradiance log | Irradiance recorded throughout the flight, so each thermal reading comes with the conditions it was taken in. |
| PDF, CSV and KML exports | A readable report, a fault list for your work-order system, and a map layer for Google Earth or GIS. |
| IEC TS 62446-3 | Inspections built to follow IEC TS 62446-3, with on-site irradiance logged for every flight. |
Select a finding on the map or in the list. Every value in this sample is made up to show the report format. A delivered report adds coordinates for each module, the source frames, and the full irradiance log.
04 / Why Orithian
Built to inspect the whole site, more often, for less.
Three of these are design goals we will verify in flight testing this winter. They are marked as such.
-
01
Design goal
The whole site in one flight
OR-2 takes off vertically like a multirotor and cruises on a fixed wing. Wing-borne flight is what makes covering a utility-scale site in a single flight practical.
-
02
Design goal
Frequent inspection at lower cost
Fewer flights and less time on site per inspection bring the cost down far enough to inspect several times a year instead of once.
-
03
Design goal
RTK, module-level accuracy
RTK-corrected positioning places each fault on a specific module, so a technician walks to one panel, not one row.
-
04
Today
A local Southern California team
We are based in Los Angeles. Southern California sites are a drive away, so follow-up flights are easy to schedule.
Edgar Reyes, Co-founder · Brandon Ly, Co-founder
05 / How we build
Built in-house, improved every week.
We design OR-2 ourselves and 3D-print its airframe on our own printers. That keeps the aircraft, and the schedule for your inspections, in our hands.
-
01
Improvements reach you quickly
When we find something to improve, we change the design and print new parts ourselves. There is no outside supplier to wait on.
-
02
Fast repairs
If a part is damaged, we print a replacement. A broken part doesn't hold up the schedule.
-
03
A lower cost for each inspection
Making the aircraft ourselves keeps its cost down, and with it what each inspection costs you.
06 / How to start
Design partner offer
We're inspecting a small number of Southern California sites at no cost this winter. You pay only if the report is useful to your team.
Become a design partner- You getA full inspection and report, as described above
- We needSite boundary and layout, an on-site contact, and a flight date
- Who will flyAn FAA Part 107-certified remote pilot
07 / The aircraft
OR-2, a VTOL fixed-wing aircraft we design and build.
It takes off and lands vertically from a small area and flies on its wing over the arrays. We will publish measured specifications after flight testing.
- Model
- OR-2
- Configuration
- VTOL fixed-wing
- Status
- In development, first flights this winter
- Specifications
- Published after flight testing
08 / Team
Founders
Based in Los Angeles.
-
Edgar Reyes
Co-founder
Edgar is an aerospace structures engineer with a B.S. in Mechanical Engineering from UCLA. As CTO of UAS@UCLA, he built autonomous drones for competition.
-
Brandon Ly
Co-founder
Brandon is a mechanical engineering student at UCLA and president of UAS@UCLA, the university's autonomous drone team.
09 / Contact
Tell us about your site.
For solar operators and asset owners. Send the basics and we will reply by email about scheduling an inspection.
Research partners and investors
For hardware, research or investment conversations, send a short note.