Solar service teams
Prioritize field follow-up with organized observations tied to an agreed array, row, or work area.
Organize thermal abnormalities, potential hotspots, and visible context across accessible solar arrays so a qualified solar or electrical professional can prioritize closer review.
Thermal aerial imagery can show temperature differences and potential hotspots across solar panels, PV modules, and array areas. Those abnormalities may help a qualified technician decide where to investigate next, but an image alone does not identify the electrical cause, confirm a failed component, measure production loss, or prescribe a repair.
The mission is planned around the array layout, available records, system operating status, target components, site access, sun and cloud conditions, wind, reflections, obstructions, safe stand-off distance, and the deliverable the maintenance team needs. Large roof arrays, carports, and ground-mounted systems may require different routes and coordination.
Visible companion images can add context for module condition, soiling, shade, vegetation, obvious damage, row position, and site orientation. Final electrical conclusions, shutdowns, testing, warranty decisions, and repairs belong to the appropriately qualified solar or electrical professional.

Richard Hamilton works directly with solar service teams, installers, property managers, and asset owners to define the array areas and information the reviewer needs. Thermal and visible images are planned for useful conditions and organized by roof, array, row, or section.
Prioritize field follow-up with organized observations tied to an agreed array, row, or work area.
Document accessible portions of a system during commissioning follow-up, warranty work, or closeout support.
Create a current visual and thermal record to share with the company responsible for electrical review.
Support maintenance planning without treating aerial temperature differences as a final fault diagnosis.
Only the approved site areas, views, sensors, timing, and outputs are included. Suitability is checked before scheduling.
Accessible modules and rows are captured using an agreed route and viewing geometry when conditions support useful observations.
RGB images add context for array position, obstructions, surface condition, shade, and obvious visible damage.
Files can be grouped by roof, array, row, section, or another site naming plan supplied before the flight.
A follow-up capture can be scoped after maintenance when the target area and comparable operating conditions are defined.
Selected thermal views from the agreed array coverage in the file format listed in scope.
Companion images to help locate and understand observations across the site.
When included, an index or marked reference can connect selected images with the client-provided array naming system.
The delivery can record date, covered areas, major conditions, and known limitations relevant to review.
The client or site representative is responsible for confirming the required system operating condition and safe access.
Fast cloud changes, low loading, glare, and reflections may reduce consistency or require a different capture window.
Roof pitch, rows, carports, vegetation, equipment, setbacks, and neighboring property affect route and visibility.
No flight is reserved by a form submission. Scope, conditions, quote, and scheduling must be confirmed.
Send the exact address or map pin, site contact, service needed, target date, and any access rules.
We review the site, flight constraints, capture plan, deliverables, timing, and quote before scheduling.
The site contact confirms access, safety requirements, active work zones, and the best window for useful data.
We complete the agreed flight when conditions allow, organize the approved outputs, and send them through the agreed delivery method.
Review local operating context, then use one project form for the exact property.
These answers are visible on the page and match the structured data.
Send the exact site, array type, site contact, available layout or naming plan, target concern, system status requirements, desired deliverable, and target date.
No. Temperature patterns can reflect operating conditions, shade, reflection, soiling, geometry, environment, or other causes. A qualified technician determines what follow-up is needed.
Both can be reviewed when the exact site, access, array geometry, operating requirements, flight constraints, and useful capture window are confirmed.
Yes when the client provides a clear naming plan or layout and that reference work is included in the scope.
Use the form for the exact location, inspection type, property, timeline, and contact details. Add the asset, expected deliverables, access rules, and the decision your team needs the imagery to support.
Submitting the form starts a review. It does not reserve a flight, confirm site suitability, or promise a result. Commercial pricing is prepared after the scope is reviewed.
One short form routes the project to the Sun State UAS team.
Form not loading? Call (561) 562-4522.