Start with the operator, not a brightness number.
“Sunlight readable” and “NVIS compatible” describe different demands. The first concerns usable information under ambient light. The second concerns operation with a specified night vision imaging system. A daylight luminance figure and a low dimming setting cannot, by themselves, specify the finished display.
Write down the application, the information the operator must read, viewing distance and angle, and the intended day-to-night workflow. Include controls, indicators and light leakage around the display, not only the LCD’s active area.
State whether the operator reads the display with unaided vision while wearing NVGs, looks directly through the goggle optics, or uses both arrangements. Direct viewing introduces its own focus, working-distance and image-legibility questions. Specify and evaluate the actual arrangement rather than assuming an NVIS label covers every goggle and use case.
Give daylight and NVIS modes separate acceptance criteria.
- Daylight: define ambient illumination, light direction, reflections, viewing angles, displayed content and the minimum readable information.
- NVIS: identify the goggle equipment and configuration, required emission performance, usable dimming range, color and uniformity.
- Transitions: define how modes are selected, what happens at startup and how unintended bright output is prevented in the operating procedure and design.
- Installation: include touch layers, cover glass, bonding, coatings, enclosure, nearby lighting, power, interfaces and temperature range.
For daylight performance, optical bonding and a suitable front-surface AR coating can address reflections before backlight power is increased. Evaluate the final stack in both modes: a change that improves one operating condition must still satisfy the other.
Which MIL-STD-3009 Type and Class are required?
Type describes the NVIS image presentation; Class describes its spectral compatibility characteristics. They are separate designations, not quality grades or LCD panel types.
- Type I: direct-view image NVIS using Generation III intensifier tubes; the intensified image is presented on a phosphor screen in the user’s line of sight.
- Type II: projected-image NVIS using Generation III tubes; the image is projected onto a see-through medium.
- Class A: associated with a 625 nm minus-blue objective filter.
- Class B: associated with a 665 nm minus-blue objective filter.
- Class C: includes a green spectral transmission window (“green leak”), used for compatibility with certain HUD arrangements. The base standard assumes Class B-compatible lighting is also compatible with Class C NVIS.
The Type I term “direct-view” describes the NVIS architecture; it does not establish that an LCD can be read directly through the goggles. Confirm that viewing requirement separately.
Ask: “What MIL-STD-3009 Type (I or II) and Class (A, B or C) are being sought?” Include the goggle model/configuration and applicable specification. If unknown, say “not sure yet”; identifying the right requirement is part of the initial discussion.
Definitions: MIL-STD-3009 §§1.3 and 3.1.1–3.1.5. See the base standard and official document status. The full spectral curves and applicable limits govern; a wavelength label alone is not a complete filter specification.
MIL-STD-3009 in the development and test plan.
MIL-STD-3009 establishes NVIS-specific emission requirements for aircraft lighting and display equipment. The official record lists the 2 February 2001 base document, an administrative notice and Notice 2 validation dated 4 April 2024. A validation notice is not a newly written technical edition.
Identify the contractually applicable document and provisions, equipment configuration and acceptance conditions. General display readability, environmental performance and installation approval need their own requirements alongside the NVIS provisions.
Turn the specification into a test matrix. For each requirement, record the assembly configuration, operating mode, test method, acceptance limit, responsible party and evidence to retain. Agree this before prototype testing so that a successful demonstration is not mistaken for completion of every required verification.
Development evaluation
Compare design options, find leakage or uniformity problems, refine mode control and evaluate readability. Record changes and the conditions used.
Acceptance evidence
Evaluate the agreed production configuration against the specified requirements using suitable methods and equipment. Retain configuration details, results and any exceptions.
These are recommended planning steps, not a substitute for the standard’s applicable procedures. For civil rotorcraft, the FAA’s NVIS resources separately address daylight, unaided, NVG cockpit and flight evaluations—illustrating why a display component test and an installation evaluation have different scopes.
DO-160 compliance: specify the environment and the evidence.
For an avionics display, optical performance must fit the environmental qualification plan. RTCA DO-160 defines environmental test conditions and procedures for airborne equipment. Agree the document issue, applicable sections and categories for the installation, then define the equipment performance that must be maintained during and after those tests.
Relevant areas may include temperature and altitude, temperature variation, humidity, shock, vibration, power input and electromagnetic susceptibility or emissions. The required categories depend on the installation; a general “DO-160 compliant” label is less useful than a qualification record tied to the actual configuration.
Keep three requirements clear: DO-160 environmental qualification, sunlight readability under defined illumination and viewing conditions, and MIL-STD-3009 NVIS compatibility. Passing one set does not establish the other two. Record the applicable tests, acceptance criteria, results and any limitations.
FPD.DEV’s expertise includes finding solutions when standard approaches fall short. We can help investigate the constraints, develop optical, electrical, thermal or mechanical changes, and define the verification needed to demonstrate the agreed requirements. This is particularly useful when brightness, heat, NVIS filtering and available space pull the design in different directions.
References: RTCA’s DO-160 overview and FAA AC 21-16G. Requirement planning was cross-checked against DO-160G §§1, 2.8–2.9 and Appendix A; use the issue and changes applicable to your project.
Experience developing and testing display devices.
FPD.DEV draws on Diggy Breiling’s experience developing and testing display devices, together with his background in optical bonding, backlight development and rugged display integration. That experience informs the practical questions: what needs to be changed, how the assembly will be built and what evidence will show that it meets the agreed need.
Start with the required performance and qualification evidence, then choose a suitable display architecture. If a commercial off-the-shelf (COTS) LCD is the starting point, enhancements can be assessed against those requirements; a custom assembly may be needed. Where supply is a constraint, options can include existing LCD cell glass, resized glass where suitable, custom TABs, TCON, backlight and housing, or custom glass when required.
The project scope should name who performs each development and acceptance activity. A filter specification, a visual demonstration or an individual component result does not automatically establish compliance of the complete display or aircraft installation.
What to send with an initial inquiry.
- Application: simulation, avionics or other equipment; new development or replacement.
- Display: model, size, resolution, interface and available drawings.
- Viewing task: goggles used, viewing arrangement, distance and angle.
- Operating conditions: daylight environment, night mode, power and thermal constraints.
- Requirements: the MIL-STD-3009 Type (I/II), Class (A/B/C), applicable provisions, applicable DO-160 issue/sections/categories, other specifications and required test evidence—or “not sure yet.”
- Build plan: prototype needs, anticipated quantities, supply concerns and timing.
Missing details are normal at the start. Send what you know; we can help identify the next questions.
Discuss an NVIS/daylight displayContinue exploring.
NVIS and daylight display engineering services →
NVIS display compatibility fundamentals →
Optical bonding and AR versus a brighter backlight →
Technical references: the official MIL-STD-3009 record and FAA NVIS evaluation resources. Examples and planning recommendations are explanatory; no project test results or certification are asserted here.