Bellerophon 1.3.0

Enterprise Documentation

Bellerophon Enterprise 1.3.0 · Product Overview · LNB Federal Corporation · October 2026

1. Overview

Bellerophon is a flight test data platform developed by LNB Federal Corporation. It reads flight test recordings in the IRIG 106 Chapter 10 format, converts recorded measurements into engineering units using a parameter dictionary, and gives a test team one shared library in which to index flights, plot parameters on a common time axis, search every flight for test conditions, and find limit exceedances.

Bellerophon Enterprise is the licensed, installable edition. It runs on a server inside the customer's network, serves many users through a web browser, processes recordings of up to 100 GB each by default (configurable), and keeps an audit log. It makes no connections to LNB Federal or to any other outside system.

Bellerophon is available to government agencies and to companies, universities and other organizations, subject to U.S. export control laws. See Eligible Customers under Legal.

About this document. This is the public overview of Bellerophon Enterprise for program offices, contracting officers and security reviewers. The complete User, Administration and Security Guide, including installation, configuration, the parameter dictionary reference and security configuration, is delivered with the licensed software.

Important: Bellerophon is a post-flight analysis tool. It is not a safety-of-flight system and is not certified for real-time range safety, flight control or airworthiness decisions. Verify any result against the program's approved data reduction before relying on it for a safety or certification decision.

2. Features

Flight Library

Indexes each recording by sortie, date, test article and duration, read from the recording's TMATS setup record and IRIG time packets.
Shows which data types each recording contains and lists limit exceedances found when the recording was processed.

Flight Detail

Stacked time history charts on a shared time axis, with an IRIG time readout at the cursor, drag to zoom and double-click to reset.
Limit lines and shaded exceedance bands, and a table of exceedances that zooms to each event.
Ground track drawn from latitude and longitude parameters and linked to the chart cursor, on a coordinate grid or on offline map tiles supplied by the customer. No maps are loaded from the internet.
Data quality: every recording receives a rating from checks on time, packets, PCM sync and subframes, MIL-STD-1553 errors and dropouts, and each parameter (no data, stuck values, values outside the valid range). Administrators set the thresholds, and the findings export as CSV.
Test points: test cards with a time window and pass or fail criteria, evaluated automatically against every recorded sample of the recording, shown on the time history and searchable across the library.
Post-flight report: one click produces a report with plots, statistics, exceedances, data quality and test point results, printable to PDF on Letter or A4 paper. Report templates set the content for each program.
Notes: engineers add time-stamped notes to a flight, such as a test point, an abort or an observation. Notes are drawn on the time history and open the chart at that moment.
Data export: the selected parameters for the current time window, written as CSV at the full recorded rate for MATLAB, Python or Excel.
Recorder inventory: channels and data types, MIL-STD-1553 traffic by remote terminal and subaddress, PCM stream status with sync errors, ARINC 429 labels, discretes, analog channels, Ethernet flows and the full TMATS record.

Search and Limits

Searches every flight in the library for intervals that meet one or more conditions at the same time, held for a minimum duration. Example: Mach above 0.9 and pressure altitude above 25,000 ft for at least 5 seconds.
Each result opens the flight zoomed to the matching interval.
Limit monitoring lists every exceedance of every dictionary limit across the library.
Exceedance report: every exceedance in the library, with sortie, parameter, limit, IRIG start time, duration and peak, as a CSV file for test reports.

Compare Flights

Overlays one parameter from up to four sorties on elapsed time, with minimum, maximum and mean for each, computed from every recorded sample in the window.

Parameter Dictionaries

Import from the TMATS setup record of a recording: PCM, MIL-STD-1553, discrete and analog measurements with units, conversions and limits. A preview lists every measurement that could not be imported, with the reason, before anything is saved.
Import from CSV with row-by-row validation; each error names the line and the field to correct. Dictionaries export to CSV and can be edited as a new version.
Linear and polynomial conversions to engineering units, limits, and valid ranges used by the data quality checks.
Derived parameters: calculated parameters such as Mach number, unit conversions and filtered signals, written as expressions with arithmetic, comparison and logic, and functions including a low-pass filter, rate of change, integral and delay. Derived parameters can be searched, plotted, compared and exported like recorded parameters.
A dictionary is applied automatically when its program name matches the TMATS program name in the recording, or it can be assigned to a flight by hand.

Data Access

A documented, read-only data access interface for recordings, parameters, time series, statistics, exceedances, data quality and test point results, used with personal access tokens that each user creates and revokes.
A Python client, written with the Python standard library only, that saves time series as CSV or MATLAB files, and as HDF5 or Parquet files when the standard h5py or pyarrow package is installed, for analysis in MATLAB, Python or other tools.
Every data access is recorded in the audit log.

Server and Administration

User accounts with three roles: administrator, engineer and viewer.
Sign-in with a password or with a smart card (CAC or PIV) through the customer's TLS reverse proxy. Password sign-in can be turned off.
Streaming upload and processing, so recordings of tens of gigabytes can be processed on ordinary hardware.
Full-flight views of millions of samples load in a fraction of a second.
Configurable system use notification at sign-in and an audit log of security-relevant actions, with the client address of each entry. Administrators page through the full log and export it as CSV for assessors.
Long library-wide searches do not delay other users.

3. Supported Data

Data type	Chapter 10 data type	Support in this release
TMATS setup record	0x01	Decoded, including the PCM format (P) groups and the recorder channel map (R); measurement definitions can be imported into a dictionary
Time Format 1	0x11	Decoded, IRIG day-of-year and month-and-year formats
MIL-STD-1553 Format 1	0x19	Decoded at word level; 16-bit and 32-bit values; bit fields
PCM Format 1	0x09	Decoded in packed and unpacked modes with intra-packet headers, using the TMATS frame definition, including words of different lengths; subcommutated parameters by subframe ID word
PCM Format 1, throughput mode	0x09	Decoded: minor frames found by searching for the TMATS sync pattern
ARINC 429 Format 0	0x38	Decoded; labels in octal; BNR and discrete fields; SDI and bus selection
Discrete Format 1	0x29	Decoded; individual bits or multi-bit fields
Ethernet Format 0 and Format 1	0x68, 0x69	Indexed with a flow summary (addresses, protocol, ports, frame counts); parameters decoded from IENA positional and fixed-layout iNET-X packets in UDP
Analog Format 1	0x21	Decoded when all subchannels share one sample rate, sample length (up to 32 bits) and packing mode
Video, image, UART, CAN and other types	various	Counted per channel; not decoded

"Decoded" means Bellerophon extracts parameter values from the data and converts them to engineering units. "Indexed" means Bellerophon reads the packets, counts them and reports their contents, but does not extract parameter values.

4. System Requirements

Node.js 22.5 or later. No other software or third-party packages are required.
Linux (recommended), Windows Server or macOS. Four CPU cores and 8 GB of memory are sufficient for most programs.
Disk space for the original recordings plus decoded data. Decoded parameters need about 16 bytes per sample. Example: 200 parameters sampled at 50 Hz for a 2-hour flight is 72 million samples, or about 1.2 GB of decoded data.
A TLS reverse proxy (for example nginx or Apache) for access across the network.
Deployment as a system service or a container on a server the customer controls, including closed and air-gapped networks.

5. Security Overview

Closed networks: the server and its web interface make no outbound connections and load no external resources.
Access control: administrator, engineer and viewer roles, with a configurable system use notification at sign-in.
Authentication: smart card (CAC/PIV) sign-in through the customer's TLS reverse proxy, or passwords with length requirements, salted password hashing, and sign-in throttling and lockout.
Cryptography: an optional FIPS mode in which Bellerophon starts only when Node.js runs with a FIPS provider enabled, for use with the customer's FIPS 140 validated cryptographic module.
Data access tokens: personal, read-only, revocable by the user or an administrator, and never stored in readable form.
Sessions and requests: protected session cookies, cross-site request forgery protection and a strict Content Security Policy.
Uploads and storage: uploads are accepted only when they begin with a valid Chapter 10 packet; on Linux and macOS, data files are readable only by the service account.
Audit: security-relevant actions are logged with time, user and client address, and administrators export the log as CSV for assessors.

Each release includes a security approval package for the customer's assessor, with the system boundary, a hardened deployment guide aligned with the applicable DISA STIG requirement areas, a NIST SP 800-53 Revision 5 control mapping and test evidence, and a software bill of materials listing every file. Detailed security configuration and settings are provided to the licensee's information system security officer with the software.

Shared Responsibilities

Area	LNB Federal Corporation	Licensee
Software	Delivers the Software, corrects reproducible defects and releases updates during the support term	Installs updates and keeps a supported Node.js version
Host and network	Documents requirements and recommended settings	Operates, hardens and patches the host, network, TLS proxy and backups
Authorization	Provides documentation to support an assessment	Obtains any required authorization to operate before operational use
Accounts	Provides role-based access and audit records	Approves users, assigns roles and reviews the audit log
Data	Has no access to Licensee data unless the Licensee grants it in writing for support	Owns its recordings and dictionaries and decides how they may be processed and marked

Authorization: Bellerophon has not been assessed or authorized under the Risk Management Framework, holds no authority to operate, and is not approved for processing classified information. The licensee is responsible for obtaining any required authorization before operational use and for operating Bellerophon under its own security controls.

6. Licensing

Bellerophon Enterprise runs under a license file issued by LNB Federal Corporation for each order. The file names the licensee, the order, the tier, the number of active users, the number of servers and the license term.

The license is verified offline by its digital signature. Bellerophon never contacts LNB Federal Corporation or any license server, and reports no usage.
Users see a renewal notice before the end date, which allows time for a renewal order.
A 30-day grace period follows the end date with full use.
After the grace period Bellerophon becomes read-only: browsing, plots, search and export continue, so a customer always keeps access to its own data. Uploads and processing resume when a renewal is installed.

7. Validation and Performance

Bellerophon's Chapter 10 reader is tested against two independent open-source readers, pychapter10 and irig106lib, on published sample recordings. All 67 checks pass. Packet counts, MIL-STD-1553 message counts with the timestamps and data words of the first 200 messages of each recording, every ARINC 429 word, discrete states, Ethernet frame counts and byte totals, PCM packets per channel, UDP payloads and analog samples are compared with pychapter10. For PCM, every minor frame is checked for the TMATS sync pattern, frame timing is checked against the TMATS bit rate, the test pattern's frame counter is checked in every frame, and minor frames found in throughput mode are compared word for word with irig106lib.

In LNB Federal testing, Bellerophon Enterprise processed a 2.6 GB recording containing 13.7 million 1553 messages and 45.6 million PCM frames at 57 MB per second, with 379 MB of peak memory. Results depend on hardware and on the number of dictionary parameters.

The capabilities added in versions 1.2 and 1.3 are verified with public sample recordings and with synthetic recordings made by the tests. Validation against the customer's own program data, compared with the program's existing data reduction, is part of each deployment.

8. Known Limitations

PCM: asynchronous and tagged embedded formats are not decoded.
Dictionaries are imported from TMATS or CSV. Import from vendor configuration formats is planned.
Ethernet: parameters are decoded from IENA and iNET-X packets with fixed layouts; other payloads are indexed.
Video, image, UART, CAN and other data types are indexed but not decoded.

9. Glossary

ARINC 429: An avionics data bus standard. Each 32-bit word carries an 8-bit label that identifies the data, a 2-bit source/destination identifier (SDI), the data field, a sign/status matrix and a parity bit.
BNR: Binary (two's complement) data encoding used in ARINC 429 words.
Chapter 10: IRIG 106 Chapter 10, the Range Commanders Council standard for digital flight data recorders. It defines the packet format that Bellerophon reads.
Dictionary: The table that tells Bellerophon where each parameter is in the recording and how to convert it to engineering units. Programs often call this a parameter list or an instrumentation database.
Engineering units: Physical units such as feet, knots or degrees Celsius, as opposed to raw counts.
CAC and PIV: Common Access Card and Personal Identity Verification card: Government smart cards that carry the holder's identity certificate.
Derived parameter: A parameter calculated from other parameters, such as Mach number from pressures.
Exceedance: A period during which a parameter is above its high limit or below its low limit.
IENA and iNET-X: Packet formats that flight test data acquisition systems use to send measurements over Ethernet.
IRIG time: Day of year, hours, minutes and seconds, from the recorder's time source.
LSB: Least significant bit. Bellerophon numbers bits from 0 at the LSB.
Major frame and minor frame: A PCM stream repeats a fixed pattern of words. One repetition, beginning with the sync pattern, is a minor frame. The cycle of minor frames after which subcommutated parameters repeat is a major frame.
MIL-STD-1553: A military command/response data bus. A bus controller commands remote terminals (RT), each with an address 0 to 31, to transmit (T) or receive (R) up to 32 data words at a subaddress (SA).
PCM: Pulse code modulation telemetry: a continuous serial stream of fixed-length words arranged in frames.
Relative time counter: The recorder's free-running 10 MHz counter stamped on every packet, used to place each packet on the IRIG time line.
SFID: Subframe ID: a word in each PCM minor frame that counts minor frames within the major frame, used to locate subcommutated parameters.
Test point: A planned test condition, flown in a time window, with criteria that decide whether it was achieved.
Subcommutated parameter: A PCM parameter that appears in a given word position only in some minor frames, so it is sampled at a fraction of the frame rate.
TMATS: Telemetry Attributes Transfer Standard, IRIG 106 Chapter 9. The setup record at the start of a Chapter 10 recording that describes its channels, PCM formats and program.

10. Release Notes

Version 1.3.0

Spanish: an English / Español switch on every screen, and Spanish translations of the documentation, the security approval package, the legal notices and the license agreement (the English versions control).
Read-only data access interface with personal access tokens, and a Python client that saves CSV and MATLAB files, and HDF5 and Parquet files with standard Python packages.
Test points with pass or fail criteria, evaluated automatically and searchable across the library.
FIPS mode, a security approval package for assessors and a software bill of materials with each release.
Decoding of analog data and of parameters in IENA and iNET-X Ethernet packets.
PCM frame sync search in throughput mode and words of different lengths in one stream.
Ground track on offline map tiles supplied by the customer.

Version 1.2.0

Parameter dictionary import from TMATS, with a preview of every measurement not imported.
Data quality report and rating for every recording.
Derived (calculated) parameters.
Smart card (CAC/PIV) sign-in.
One-click post-flight report, printable to PDF, with report templates per program.
Dictionary export to CSV, polynomial conversions and valid ranges.

Version 1.1.0

Notes on flights, parameter data export at the full recorded rate, a library exceedance report and audit log export, all as CSV.
Signed license files verified offline, with renewal notices, a 30-day grace period and read-only access after expiry.
Full-resolution statistics in Compare; search and statistics in a background thread.
Decoding and timing improvements for MIL-STD-1553, Chapter 10 packet recovery and exceedance reporting.
Stricter parameter dictionary validation.
Security hardening of sign-in, sessions, uploads, file permissions and audit records.

Version 1.0.0

First release of Bellerophon Enterprise and the Bellerophon Evaluation edition.
Decoding of MIL-STD-1553, PCM, ARINC 429 and discretes; indexing of Ethernet and other data types.
Parameter dictionaries with limits; library-wide search and limit monitoring; flight comparison.
Multi-user server with roles, streaming ingest and an audit log.

LNB Federal Corporation

Legal Notices and License Terms

LNB Federal Corporation, a Delaware corporation. These notices apply to the Bellerophon software, including the Bellerophon Evaluation edition and Bellerophon Enterprise (together, the "Software"), and to its documentation. Last updated October 11, 2026 (revision 4: on lnbfederal.com, acceptance of the evaluation notice is remembered in the browser for 30 days).

How to Read These Notices

Each section below states the legal terms first. Where a section is followed by a box marked In plain terms, that box explains what the section means in practice for engineers and program staff. The plain-language explanations are provided for convenience only. They are not part of the terms, and if an explanation differs from the terms, the terms control. Contracting officers and legal counsel should rely on the terms themselves and on the applicable order.

Eligible Customers

LNB Federal Corporation ("LNB Federal") makes the Software available to government departments and agencies, companies, universities, research institutions and other organizations (each an "Eligible Customer"), subject to the Export Control Notice below, which currently limits delivery of Bellerophon Enterprise to Eligible Customers located in the United States. LNB Federal does not provide the Software to any person, country or end use prohibited by U.S. export control or sanctions laws, screens each customer against U.S. restricted party lists before delivery, and may decline to provide the Software to any person at its discretion and in accordance with applicable law. A contractor or consultant may use the Software on behalf of an Eligible Customer that holds a license or, for the Evaluation edition, that has authorized the evaluation.

In plain terms: Bellerophon is available to government agencies and to companies, universities and other organizations. Bellerophon Enterprise is currently delivered only to customers in the United States while its export classification is pending, and every order is checked against U.S. export and sanctions rules before delivery. Contractors can use it for work they are doing for a licensed customer. For questions about eligibility, contact webmaster@lnbfederal.com.

Bellerophon Evaluation Terms

These terms govern the Bellerophon Evaluation edition made available through https://lnbfederal.com (the "Evaluation Edition"). By selecting "I accept," you agree to these terms on behalf of yourself and the organization you represent, and you confirm that you are authorized to accept them for that organization, or that you are evaluating the Software for yourself as an individual. If you do not agree, or if you are not so authorized, select "Decline" and do not use the Evaluation Edition.

1. Evaluation license. LNB Federal grants you a limited, non-exclusive, non-transferable, revocable, royalty-free license to use the Evaluation Edition solely to assess whether you or your organization will license the Software. The license ends when LNB Federal withdraws the Evaluation Edition.

2. Demonstration content only. The Evaluation Edition contains synthetic demonstration flights and a demonstration parameter dictionary generated by LNB Federal. They do not represent any real aircraft, program, test or flight. The Evaluation Edition stores the demonstration data at reduced resolution, as described in the Evaluation Guide, and cannot open recordings or import parameter dictionaries.

3. No operational use. You may not use the Evaluation Edition, or any result it displays, for flight safety decisions, airworthiness determinations, certification, mission planning or any other operational purpose.

4. Restrictions. You may not copy, modify, distribute, sell, sublicense, frame or host the Evaluation Edition for others; remove or alter any notice; use it to build a competing product; or reverse engineer, decompile or disassemble it, except to the extent applicable law expressly permits despite this restriction.

5. Information you enter. Do not enter classified information, Controlled Unclassified Information, export-controlled technical data or program information into the Evaluation Edition. The Evaluation Edition does not transmit information to LNB Federal.

6. Feedback. If you provide comments or suggestions about the Software, LNB Federal may use them without obligation to you. Do not include classified, controlled or proprietary information in feedback.

7. No warranty. The Evaluation Edition is provided "as is" and "as available," without warranty of any kind, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, accuracy or non-infringement.

8. Limitation of liability. To the maximum extent permitted by applicable law, LNB Federal will not be liable for any indirect, incidental, special, consequential or punitive damages, or for loss of data, arising from use of the Evaluation Edition, and its total liability arising from the Evaluation Edition will not exceed one hundred U.S. dollars (US $100).

9. Government users. Nothing in these terms obligates appropriated funds, requires a government user to indemnify LNB Federal, or applies to a government user to the extent it is inconsistent with federal law or with the user's national law. If a provision is unenforceable against a government user, the remaining provisions continue to apply.

10. Export. Your use is subject to the Export Control Notice below.

11. Governing law. For U.S. Government users, these terms are governed by the federal law of the United States. For all other users, these terms are governed by the laws of the State of Delaware, without regard to conflict of law rules, and the state and federal courts located in the State of Delaware have exclusive jurisdiction over any dispute arising from them.

In plain terms: you may use the Evaluation edition to decide whether your organization wants Bellerophon. It works only with made-up sample flights stored at reduced resolution, so do not use anything it shows for a real flight, safety or certification decision, and do not type real program data into it. Do not copy it, host it elsewhere or take it apart. It comes with no warranty, and LNB Federal's liability for it is capped at $100. Nothing here commits government funds or overrides federal law.

Bellerophon End User License Agreement

This End User License Agreement (the "Agreement") is between LNB Federal and the Eligible Customer identified in the applicable order, contract, task order, purchase order or other signed ordering document (the "Order") (the "Licensee"). It applies to Bellerophon Enterprise and to any version of the Software delivered under an Order. For U.S. Government licensees, this Agreement is the commercial license under which the Software is offered, and it applies only to the extent consistent with federal law and the Order.

1. Definitions. "Software" means the Bellerophon software in object and script form, including updates delivered under the Order. "Documentation" means the user, administration and security documentation LNB Federal provides for the Software. "Authorized Users" means employees of the Licensee and contractors acting on its behalf whom the Licensee authorizes to use the Software. "Licensee Data" means recordings, dictionaries, decoded data and other information the Licensee processes with the Software.

2. License grant. Subject to this Agreement and payment of the fees in the Order, LNB Federal grants the Licensee a non-exclusive, non-transferable license, for the term, site and quantity stated in the Order, to install the Software on systems the Licensee controls and to permit Authorized Users to use the Software and Documentation for the Licensee's internal business or governmental purposes. The Licensee may make a reasonable number of copies for backup, disaster recovery, testing and security assessment.

3. Restrictions. Except as this Agreement or applicable law expressly permits, the Licensee will not (a) sell, rent, lease, sublicense or distribute the Software to any person who is not an Authorized User; (b) use the Software to provide services to persons other than the Licensee, including as a hosted service or service bureau, unless the Order permits it; (c) modify the Software, except for configuration described in the Documentation; (d) reverse engineer, decompile or disassemble the Software; or (e) remove or alter proprietary, export or legal notices. Nothing in this section limits rights the U.S. Government holds by statute or under the Order.

4. Ownership. The Software is licensed, not sold. LNB Federal and its licensors retain all right, title and interest in the Software and Documentation, including all intellectual property rights. The Licensee retains all right, title and interest in Licensee Data.

5. Licensee Data. The Software runs on infrastructure the Licensee controls and does not transmit Licensee Data to LNB Federal. LNB Federal will access Licensee Data only if the Licensee gives access in writing for a support purpose, and will then protect it as the Order and applicable law require.

6. Support and updates. LNB Federal will provide the support, maintenance and updates stated in the Order. Unless the Order states otherwise, support includes correction of reproducible defects and updates released during the paid support term.

7. Limited warranty. LNB Federal warrants that, for ninety (90) days after delivery, the Software will perform substantially as described in the Documentation. The Licensee's exclusive remedy for breach of this warranty, and LNB Federal's sole obligation, is for LNB Federal to correct the nonconformity, replace the Software or, if neither is commercially reasonable, end the license for the nonconforming Software and refund the fees paid for it. The warranty does not apply to nonconformities caused by modification, misuse, or use with hardware, software or data not described in the Documentation.

8. Disclaimer. Except for the express warranty in section 7 and any warranty the Order requires, the Software and Documentation are provided without any other warranty, express or implied, including implied warranties of merchantability, fitness for a particular purpose and non-infringement. LNB Federal does not warrant that the Software will be error free or that results will be accurate for every recording. The Licensee is responsible for verifying results before relying on them for flight safety, airworthiness or other critical decisions.

9. Limitation of liability. To the extent permitted by applicable law, neither party will be liable to the other for indirect, incidental, special, consequential or punitive damages, or for lost profits or data, and LNB Federal's total liability arising from this Agreement will not exceed the fees paid for the Software in the twelve (12) months before the claim arose. These limits do not apply to LNB Federal's obligations under section 10, to liability for fraud, bodily injury or death caused by negligence, or to any liability that cannot be limited under applicable law, including 31 U.S.C. §§ 3729–3733.

10. Infringement. LNB Federal will defend the Licensee against third-party claims that the Software, as delivered, infringes a United States patent, copyright or trademark or misappropriates a trade secret, and will pay resulting damages finally awarded or settlements LNB Federal approves. For U.S. Government licensees, the defense of any claim is subject to the authority of the U.S. Department of Justice under 28 U.S.C. § 516, and LNB Federal may participate at its own expense. If the Software is or may become subject to such a claim, LNB Federal may obtain the right for the Licensee to continue using it, modify it to be non-infringing, or end the license and refund the unused prepaid fees.

11. Term and termination. This Agreement lasts for the term stated in the Order. For U.S. Government licensees, termination is governed by the Order and federal law, and disputes are resolved under the Contract Disputes Act, 41 U.S.C. §§ 7101–7109. For other licensees, either party may terminate for the other party's material breach that remains uncured thirty (30) days after written notice, unless the Order provides otherwise. When the license ends, the Licensee will stop using the Software and remove it from its systems, except for copies it must keep under law or records retention rules. Licensee Data remains the Licensee's property.

12. Export. Each party will comply with the export control and sanctions laws that apply to it, as described in the Export Control Notice.

13. Governing law. For U.S. Government licensees, this Agreement is governed by the federal law of the United States. For all other licensees, this Agreement is governed by the laws of the State of Delaware, without regard to conflict of law rules, and the state and federal courts located in the State of Delaware have exclusive jurisdiction over any dispute arising from it. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

14. Government terms prevail. For U.S. Government licensees, any term of this Agreement that is inconsistent with federal law or with the Order, including any term that would require the Government to indemnify LNB Federal, renew automatically, pay taxes or fees not stated in the Order, or accept changes to this Agreement it has not signed, is unenforceable against the Government to that extent, consistent with FAR 52.212-4. The Order controls over this Agreement where they conflict.

15. General. This Agreement and the Order are the entire agreement on their subject. A waiver is effective only in writing. If a provision is unenforceable, the rest of the Agreement remains in effect. The Licensee may not assign this Agreement without LNB Federal's written consent, except as federal law permits. LNB Federal may assign it only as permitted by applicable law and the Order, including the novation requirements of FAR Subpart 42.12 for U.S. Government contracts.

In plain terms: your organization's order sets the term, the site and the number of users. Install Bellerophon on systems your organization controls and let your own people and your contractors use it for your own work. Do not resell it, run it as a service for others unless your order allows it, modify its code or take it apart. LNB Federal owns the software; your organization owns its recordings, dictionaries and results, and Bellerophon never sends them to LNB Federal. For 90 days after delivery LNB Federal will fix or replace the software if it does not work as documented. Engineers must still check results against the program's approved data reduction before using them for safety or certification decisions. If anyone claims the software infringes their rights, LNB Federal defends your organization (for a U.S. Government customer, subject to the Department of Justice's authority). For a U.S. Government order, federal law and the order itself always win over this agreement.

U.S. Government Rights

The Software is "commercial computer software" and the Documentation is "commercial computer software documentation," as those terms are used in FAR 2.101 and DFARS 252.227-7014. Under FAR 12.212 and DFARS 227.7202-1 and 227.7202-3, the U.S. Government and its contractors acquire the Software and Documentation only with the rights set out in the Bellerophon End User License Agreement, as modified by the Order. The contractor and manufacturer is LNB Federal Corporation, a Delaware corporation, CAGE 12WN4.

For government customers outside the United States, rights in the Software are those set out in the End User License Agreement and the Order, subject to that nation's procurement law.

In plain terms: Bellerophon was developed at private expense and is sold as a commercial product. A U.S. Government buyer receives the rights in the license agreement and the order, not unlimited or government-purpose rights in the source code.

Export Control Notice

The Software, the Documentation and related technical information may be subject to the U.S. Export Administration Regulations (15 C.F.R. Parts 730–774), U.S. economic sanctions administered by the Office of Foreign Assets Control (31 C.F.R. Chapter V), and the export laws of other countries. You may not export, re-export or transfer the Software, directly or indirectly, to any country, entity or person, or for any end use, prohibited by those laws, including to any person on the Entity List, the Denied Persons List or the Specially Designated Nationals and Blocked Persons List, or to any country or region subject to a comprehensive U.S. embargo.

LNB Federal reviews every order for export compliance and screens each customer against U.S. restricted party lists before delivery. A request for an official export classification of the Software has been filed with the U.S. Department of Commerce, Bureau of Industry and Security, and is pending. Until it is decided, LNB Federal supplies Bellerophon Enterprise only to Eligible Customers located in the United States and does not export, re-export or transfer it outside the United States. Contact webmaster@lnbfederal.com with any export question.

Flight test recordings and parameter dictionaries may themselves contain technical data controlled under the International Traffic in Arms Regulations (22 C.F.R. Parts 120–130) or the Export Administration Regulations. Users are responsible for handling their own data in compliance with those regulations.

In plain terms: do not send Bellerophon to a sanctioned country or a restricted party. Bellerophon Enterprise is currently supplied only to customers in the United States and must not be moved outside the United States, including to an allied country, while its export classification is pending; contact LNB Federal with any export question. Remember that your flight data and parameter lists may be export controlled even when the software is not; handle them under your program's export rules.

Classified Information and Safety of Flight

The Software has not been assessed or authorized for use on any information system under the Risk Management Framework, holds no authority to operate, and is not approved for processing classified national security information. Each Licensee is responsible for obtaining any authorization or security approval it requires before operational use and for operating the Software under its own security controls. The Evaluation Edition must not be used with classified information under any circumstances.

The Software is not a safety-of-flight system. It is not designed or certified for use in aircraft, flight control, real-time range safety or any application in which failure could lead to death, personal injury or severe property damage.

In plain terms: Bellerophon has no ATO yet. Your organization's security authority (for a government agency, its authorizing official) decides whether and where it may run. It is a post-flight analysis tool: never use it to control an aircraft or to make a real-time range safety call.

Data Handling and Privacy

Evaluation Edition. The Evaluation Edition contains only synthetic demonstration data, cannot open or upload files, and does not transmit information to LNB Federal. It uses no cookies, accounts or analytics. Your acceptance of the evaluation notice is remembered in this browser (local storage) for 30 days, then requested again; declining clears it. To display text, the page loads the Lato and IBM Plex Mono fonts from Google Fonts, which receives your network address when the fonts load, under Google's own privacy terms.

Bellerophon Enterprise. The Software runs on infrastructure the Licensee controls. It stores user names, email addresses, hashed passwords, session records, an audit log and Licensee Data on that infrastructure, makes no outbound network connections, and sends no telemetry to LNB Federal.

For the privacy statement governing the https://lnbfederal.com website, see the Privacy Statement on that site.

Trademarks and Standards

LNB Federal and the names of LNB Federal products are trademarks of LNB Federal Corporation. Other names are the property of their owners. IRIG 106 is published by the Range Commanders Council. MIL-STD-1553 is a U.S. Department of Defense standard. ARINC 429 is an aviation industry standard. References to standards, government organizations or NATO describe compatibility only and do not imply affiliation with, or endorsement by, the standards bodies, the U.S. Department of War, any other Government Agency or NATO.

Third-Party Notices

The Evaluation Edition displays the Lato typeface (Copyright Łukasz Dziedzic) and the IBM Plex Mono typeface (Copyright IBM Corp.), each licensed under the SIL Open Font License, Version 1.1. Bellerophon Enterprise contains no third-party code. It runs on the Node.js runtime, which the Licensee installs separately under the Node.js license. The container image in the Enterprise package is based on the official Node.js image, whose components are licensed by their respective owners.

LNB Federal tested the Software's Chapter 10 reader against the open-source pychapter10 library and its sample recordings (BSD 3-Clause License, Copyright Avionics Test and Analysis Corporation) and against the open-source irig106lib library (BSD license, Copyright Irig106.org). Those libraries and recordings are not distributed with the Software.