.jpg)
An airport authority board approves capital investments on two criteria: financial justification and risk management. A request that speaks only to operational improvement will get deferred. A request that connects the investment to documented liability exposure, regulatory standing, grant eligibility, and long-term insurance cost reduction is a request that gets taken seriously.
Aircraft Emergency Systems sit squarely in both categories. The financial case is real and quantifiable. The risk case is documented and the cost of inaction is measurable. What most AES proposals lack is a board-level narrative that connects those two cases in the language an airport authority actually responds to.
This article builds that narrative. It covers the four pillars of an AES investment case: regulatory risk, liability exposure, AIP funding eligibility, and long-term insurance and ISO cost reduction.
The Regulatory Risk Argument
FAA Part 139 certification requires airports to maintain documented, multi-agency emergency notification procedures. The standard is specific: every agency that responds to an aircraft emergency must be notified, the notification must happen within defined timeframes, and the process must be documented in a form that survives a post-incident review.
Manual crash phone protocols create a structural gap in that documentation. When notification happens through a sequential call chain managed by an ATC controller, the record of what was communicated, to whom, and when exists only in the recollection of the people who made the calls. That is not the same as a timestamped system log, and FAA auditors know the difference.
The exposure this creates is not hypothetical. A Part 139 certification review that finds inadequate notification documentation can result in conditions, required corrective actions, and in serious cases certification consequences that affect the airport's operating status. The reputational and operational cost of a finding at that level exceeds the capital cost of a properly deployed AES by a wide margin.
The FAA Part 139 airport alerting requirements article covers the specific documentation standards in detail. For a board presentation, the relevant framing is this: the airport is currently producing its Part 139 compliance record through a manual process that cannot generate the documentation an audit requires. That is a certification risk, and AES closes it.
The Liability Exposure Argument
An aircraft emergency that results in casualties, property damage, or a failed response will be reviewed. The review will ask whether every responding agency was notified, when they were notified, what information they received, and whether the notification process met the standard the airport's emergency plan documents.
Under a manual crash phone protocol, the answers to those questions depend on dispatcher recall, controller notes, and whatever informal documentation the tower or ARFF station happened to maintain. In a litigation context, that record is vulnerable. Plaintiff counsel understands the difference between a timestamped system log and a reconstructed account.
An AES deployment creates an automatic, timestamped record for every emergency declaration: which agencies were notified, when, what information was included, and which agencies confirmed receipt. That record does not depend on anyone's memory. It is complete, consistent, and produced without any additional documentation effort from tower or ARFF staff.
For an airport authority board that thinks in terms of institutional liability, this is a concrete and defensible argument. The question is not whether a future incident will be reviewed. It will be. The question is whether the airport's notification record will hold up in that review or create additional exposure.
The full picture of how multi-agency notification works in an AES-equipped airport is covered in the multi-agency coordination in aircraft emergency response article, including the specific gaps that sequential crash phone protocols leave in the coordination record.
FAA Airport Improvement Program Funding Eligibility
AES infrastructure qualifies for FAA Airport Improvement Program funding as an airport safety system improvement. AIP grants cover up to 90 percent of eligible project costs at non-primary commercial service airports and up to 75 percent at primary commercial service airports, with the airport authority responsible for the remainder.
That funding structure changes the capital math substantially. A system with a total project cost in the mid-six figures becomes a smaller net outlay when AIP funding is applied. For airport authority boards evaluating capital requests against constrained budgets, the availability of federal grant funding is often the factor that moves a deferred item into an active project.
The elements of a strong AIP application for AES include:
- Documentation that the current notification system has a compliance gap against Part 139 requirements
- A project narrative that connects AES to specific safety system improvement goals
- Cost documentation from a vendor with a defined scope of work
- Evidence that the airport has evaluated alternatives and selected the approach that best meets the regulatory and operational requirements
Working through the AIP application process requires coordination with the FAA regional office and the airport's designated AIP coordinator. Starting that conversation early, before a board vote, allows the funding timeline to align with the procurement and installation schedule rather than lag behind it.
Westnet's aircraft emergency systems platform is designed to meet the AIP eligibility criteria for airport safety system improvements. The procurement team can provide the scope of work documentation and project narrative elements that support an AIP application as part of the proposal process.
ISO Rating and Long-Term Insurance Cost Reduction
Airport insurance premiums are influenced by the ISO Fire Suppression Rating Schedule, which evaluates the quality of fire protection infrastructure including alerting and communications systems. A higher ISO rating correlates directly with lower insurance premiums across the airport's coverage portfolio.
The alerting and communications component of ISO ratings accounts for a measurable share of the total score. An airport operating with manual crash phone protocols and no automatic documentation of notification performance is leaving ISO rating points on the table that a properly deployed AES would recover.
The financial model for a board presentation should include a five-year insurance cost projection under the current ISO rating compared to the projected rating after AES deployment. That comparison, combined with the AIP funding offset, often produces a net present value analysis that shows the system paying for itself within the grant cycle.
For airports that have not had an ISO rating review recently, requesting one before developing the AES business case is worth doing. The review will surface the specific components where the current rating is weakest, and in most cases alerting and communications infrastructure will be among them.
The Competitive and Reputational Dimension
Airport authority boards are attentive to how their institution is perceived relative to peers. An airport that experiences a response coordination failure during an aircraft emergency, and whose post-incident review finds that notification procedures were manual and undocumented, faces a reputational consequence that extends beyond the incident itself.
Peer airports that have deployed AES have response time data, notification records, and FAA compliance documentation that positions them favorably in any comparative review. The airports that haven't are increasingly the outliers in that comparison, and the gap is visible to FAA inspectors, insurance underwriters, and airline partners who evaluate airport operational quality as part of their own risk assessments.
This is a board-level argument rather than an operational one. Airport COOs and directors who have made this case successfully report that framing AES as a peer-comparison item, rather than a safety technology upgrade, resonates with board members who are sensitive to how the airport's standing looks against comparable facilities.
The how Westnet AES improves ARFF response times article covers the response time improvement data in detail, which provides the quantitative peer comparison material a board presentation can reference.
Structuring the Board Presentation
A board-level AES capital request is strongest when it covers four areas in sequence:
- Current state and risk exposure: what the existing crash phone protocol produces in terms of documentation, notification speed, and Part 139 compliance, stated in specific and factual terms
- Financial case: AIP funding eligibility and estimated grant offset, ISO rating improvement and five-year insurance cost delta, and total net cost after grant funding
- Liability and regulatory case: the documentation gap under manual protocols, the cost of a Part 139 finding, and the liability exposure in a post-incident proceeding
- Implementation: timeline from board approval to operational deployment, procurement vehicle, and reference airports using the same system
The procurement vehicle matters for the board presentation for the same reason it matters in fire department capital requests. A purchase through a cooperative contract like Sourcewell or GSA has already gone through competitive solicitation. Board members who are concerned about procurement compliance will want to know the purchase method before voting on the capital item.
For airports planning a full review of emergency alerting infrastructure across both the airfield and the terminal environment, Westnet's fire station alerting solutions and AES platform are designed to work as an integrated system, which simplifies the procurement, installation, and support relationship compared to managing separate vendors for each component.
The Cost of Waiting
Airport capital planning cycles create natural deferral points. An AES request that misses the current cycle gets pushed 12 to 18 months, during which the airport continues to operate with a notification system that cannot produce a defensible compliance record and continues to carry the liability exposure that manual documentation creates.
That deferral has a cost that doesn't appear on a balance sheet until something happens. The argument for timing is straightforward: AIP funding availability, ISO rating improvement, and liability risk reduction all favor acting within the current capital cycle rather than the next one.
The board presentation should make that timing argument explicitly, including what the estimated insurance premium cost is for the deferral period and whether the AIP funding window the airport intends to use has a grant cycle deadline that affects the project timeline.