Define a pass before judging the picture
A low-light FPV video test is useful when one named camera-to-display configuration meets a predefined criterion under recorded conditions. A brighter image alone is not a pass. Separate the requirements for pilot viewing, recording and any model-specific onboard processing.
Describe the scene and motion
Record the illumination, contrast, target size in the image, working distance, lens, field of view and motion represented by the evaluation setup. Include bright-to-dark transitions or glare only where they belong to the intended operating envelope. Label controlled test scenes so they are not mistaken for field validation.
Check the delivered image
Evaluate the image at the receiving display as well as the camera output. Look for lost edges, motion blur, clipped highlights, temporal noise, missing frames and changes after encoding. Exposure and processing settings that improve a still image may have different consequences during motion.
Keep optional thermal input separate
Thermal input is a separate scene and interface requirement. Record its exact module, lens, display path and test conditions. A thermal image does not by itself prove that it can replace the pilot video path or that visible and thermal channels are calibrated or synchronized.
Use a reproducible acceptance record
Keep the hardware and firmware revisions, camera settings, power, cabling, receiver, display and measurement boundary with the result. Record what passed, what failed and which conditions were not covered. Do not convert one selected scene into a universal night-performance claim.
Choose the next engineering step
For a module-selection review, provide the required output, receiving equipment, mounting envelope and representative low-light conditions. Agree what a sample must demonstrate before treating it as a candidate for an FPV design-in. Final aircraft and operating validation remain customer-owned.