When an aircraft, missile or projectile is tested, someone has to prove what it did. Radar and telemetry carry much of that load, but ranges still rely on optical tracking: telescopes and long lenses on tracking mounts that record the object frame by frame. Those images show attitude, separation, deployments and impact in a way numbers alone cannot.
This post covers how to think about a cooled scientific camera for range and flight-test tracking, and the questions to settle before you choose. We use Finger Lakes Instrumentation (FLI) cameras as the worked example. Tracking satellites from the ground is a related problem with its own constraints; we cover it in our post on daytime satellite tracking for SDA.
What a test-range tracking camera has to do
The target moves quickly across the sky, the mount has to keep it near the center of the field, and the event may last seconds. There is rarely a second chance. If the exposure was wrong or the trigger missed, the test may have to be flown again.
That puts four demands on the camera. It has to handle a bright, changing background without saturating. It has to sample the optics finely enough to resolve the details the test needs. It has to freeze motion with short exposures. And it has to run reliably at a remote site, tied to the range's timing.
Sensitivity, dynamic range and the bright-sky problem
Most flight tests happen in daylight. Against a bright sky, the background often fills pixels faster than the target does, so the limit is usually dynamic range rather than raw sensitivity. A single scene can also hold a dim airframe next to a very bright plume, flare or sunlit glint.
A camera for this work needs headroom at the top of its range and low noise at the bottom. FLI Kepler CMOS cameras address this with a high-dynamic-range readout: the 16-bit image combines two 12-bit readouts at different gains, with less than 1% non-linearity. Set exposure from the brightest feature you must not clip, then confirm the dim features you care about still sit well above the noise.
Filters help too. A long-pass filter can cut blue sky background, and a neutral density filter can tame a plume.
Field of view versus sampling
Every tracking system trades field of view against detail. Pixel scale is pixel pitch divided by focal length. A 9 µm pixel behind a 1,000 mm focal length lens covers 9 µrad, so at 20 km each pixel spans about 18 cm.
A larger sensor gives more field at the same pixel scale, which leaves room for tracking error and for objects that separate. The KL4040FI uses a 4096 × 4096 sensor with 9 µm pixels and a 52.1 mm diagonal. The KL6060FI uses a 6144 × 6144 sensor with 10 µm pixels and an 86.9 mm diagonal. At 1,000 mm, the KL4040FI's 36.9 mm side gives a field roughly 2.1° wide.
Near-horizontal paths add turbulence and haze that often blur the image more than the optics do, so sampling far finer than the atmosphere allows only adds data. Our post on pixel size and sampling covers the matching math in detail.
Freezing motion without starving the signal
Angular rate is transverse speed divided by range. An object crossing at 300 m/s, 20 km away, moves about 15 mrad/s. Without tracking, a 1 ms exposure would smear it across almost two 9 µm pixels at 1,000 mm. A good mount removes most of that motion, and the residual tracking error is what the exposure has to freeze. With 1 mrad/s of residual error, the same 1 ms exposure smears only about a tenth of a pixel.
Shorter exposures freeze motion but collect less light. In daylight there is usually signal to spare. At dusk or at night, the balance shifts, and low read noise matters more. Kepler cameras are designed for fast, continuous, short-exposure imaging.
Shutter mode matters for fast targets. Kepler sensors use a rolling shutter with a global-reset mode; they do not have a true global shutter. In rolling mode, rows expose at slightly different times, so a fast target can appear skewed. Keep the target well tracked, or use global reset where the lighting allows.
Triggering from the range timing system
Range imagery has to line up with other cameras, radar, telemetry and the test article's own events. That alignment should come from the range timing system, not from each camera's software clock. Independently timed cameras drift.
External trigger in and out is standard on FLI Aurora cameras and listed on Kepler data sheets. A range timing unit can turn its master time into trigger pulses for every camera at a site. Account for each sensor's fixed delay; for example, an Aurora in triggered global-reset mode has a row-reset delay of roughly 300 to 350 µs. Our post on synchronizing multiple cooled cameras covers trigger planning and timing checks.
Building for remote pads and long runs
Tracking sites are often remote and exposed to sun, dust and temperature swings. Check the operating range for your model; the KL4040, for example, is rated for 0 to 40 °C operation, and anti-dew is recommended at cold sites.
All Keplers are air-cooled as standard and plumbed for liquid circulation, which helps in hot enclosures. Our post on air versus liquid cooling explains the trade-offs. User-replaceable shutter, fans, and digital board make Kepler ideal for remote installations. FLI cameras already operate in observatories from the high arctic to the Antarctic. Since inception, fewer than 1% of FLI cameras have failed in their first five years.
Cable runs are the other remote-site issue. Kepler cameras connect over USB 3.0. Beyond about 3 m, use an active USB extender or USB-over-fiber.
Software, interfaces and a defense paperwork baseline
Most range systems run their own acquisition and pointing software. FLI provides the Kepler SDK for Windows and Linux, and many customers wrap it in their own code. In a hardware-triggered loop, abort the capture after every triggered frame, including after a timeout. SDKs and manuals are on our support page.
Range equipment also comes with paperwork. FLI operates under AS9100D / ISO 9001:2015 · ITAR compliant · CMMC Level 2 compliant. We machine housings in-house, finish and test boards, and test every camera before it ships. Our defense camera supplier checklist covers qualification, and our post on cameras in secure facilities covers the security review.
Questions to settle before you choose
- What focal length and aperture will the mount carry, and what pixel scale do you need?
- What are the closest and farthest ranges, and the fastest angular rates?
- How well does the mount track, and what residual error must the exposure freeze?
- Will tests run in daylight, at dusk, at night, or all three?
- How bright is the brightest feature compared with the dimmest one you must measure?
- What timing signal will drive the trigger, and what delay can you tolerate?
- How far is the camera from the host, and what is the site's temperature range?
Talk to our sales team
Send our sales team your optics, target ranges and angular rates, lighting conditions and timing setup, and we will suggest the standard camera configuration that fits. If a program needs a modest change to a standard camera, we are glad to discuss it. Request a quote or email sales@flicamera.com. To see where FLI cameras are used across research, defense and industry, visit our applications page.
FLI cameras are Made in USA, and our sensor chambers are assembled in our 1,000+ sq ft ISO Class 7 clean room. See how on our in-house manufacturing page.
