Skip to main content

Morning Overview

The FAA wants $170,000 from a California airport that let flights go without fire crews

On two days in March 2025, passenger airliners operated at a county-owned airport in Santa Rosa, California, while the crash trucks and firefighters that federal rules say must stand ready were not there. The Federal Aviation Administration says nobody told the airline, either.

On Nov. 12, the agency proposed a $170,000 civil penalty against Charles M. Schulz Sonoma County Airport, code STS, over the two flights. The money is not final: the airport has 30 days after receiving the notice to respond.

Two flights, one skipped wildlife sweep

According to the FAA’s announcement, the airport lacked the required aircraft rescue and firefighting personnel and vehicles on two passenger flights in March 2025. The FAA says the airport’s own FAA-approved Airport Certification Manual required it to tell the airline when that coverage was missing, and that no such notice went out. A second allegation concerns animals: for one of the same flights, the agency says airport staff skipped the runway check for deer and other wildlife that the airport’s FAA-approved wildlife hazard management plan requires before the first flight of the day. The release names no airline and no flight numbers, carries no statement from an FAA official, and includes no response from the airport. AvWeb, which reported the case on Nov. 13, likewise could not identify the carrier.

The three-minute rule in 14 CFR 139.319

The requirement sits in 14 CFR 139.319. Airports certificated for airline service must keep rescue and firefighting capability available “during air carrier operations at the airport,” and the rule says “sufficient rescue and firefighting personnel are available during all air carrier operations.” The required capability level is tied to an Index set in a companion section, and it must rise if an airport’s average daily departures or the length of the aircraft using it grow, so a busier airport owes more equipment and more people. The same section sets a clock. Within three minutes of an alarm, at least one required vehicle must reach the midpoint of the farthest air carrier runway and begin applying extinguishing agent; any other required vehicles must arrive within four minutes.

When capability drops, the rule is equally specific about what an airport owes the airlines. A reduction may not be implemented “unless notification to air carriers is provided,” through the Airport/Facility Directory or a NOTAM plus direct contact with local carriers.

The FAA’s Jan. 30, 2024 CertAlert 24-01 goes further for the worst case, which it calls ARFF Zero: with no operational capability at all, a certificate holder must immediately issue a NOTAM closing the airport to air carrier operations. Notice is the hinge of the Sonoma allegation. A flight can go ahead with a thin safety margin that the airline knows about; the FAA’s complaint is that the airline was never told the margin had vanished.

A staffing warning from October 2024

The March 2025 flights were not the first sign of strain at the airport. AvWeb recounted that in October 2024, KQED reported airport personnel missed the three-minute response requirement during an unannounced FAA inspection, which followed employee complaints about too few people covering aircraft emergencies. Sonoma County supervisors then approved two additional airport operations specialist positions. Airport manager John Stout told a county meeting that month, as AvWeb relayed from KQED, that more staff was needed as passenger growth continued, both in the office and in the field.

The FAA’s release does not link that inspection to the proposed penalty, and nothing in it says what staffing looked like on the two March 2025 days. The connection is background, not a finding. It does show that emergency-coverage staffing at STS was already a question in county government well before the FAA’s notice.

Where $170,000 sits among earlier firefighting cases

In December 2021 the agency proposed $167,343 against Dayton, Ohio, alleging that John M. Cox International Airport allowed seven flights on Feb. 13, 2020 while short of required firefighting vehicles and without notifying the FAA or carriers. Dayton’s one-day total covered seven flights; Sonoma’s covers two flights plus the wildlife check, and the FAA does not break its figure down between the allegations.

Larger numbers appear when the gap is long. A June 2023 proposal against Alamosa, Colorado, put the penalty at $1,290,780, alleging that about 138 scheduled air carrier flights between November 2020 and September 2021 took place with no firefighters on the airport. That airport’s manual calls for qualified firefighters on site at least one hour before the first scheduled airline operation of the day, 45 minutes before each later one, and for 15 minutes afterward.

Smaller penalties involve training records. A March 2020 case at King Salmon, Alaska, produced a $79,500 proposal after an employee on standby for three flights in April 2019 had gone more than a year without a live-fire drill. In each case the FAA frames its findings as allegations. What happens next at Sonoma is open: the airport can answer within the 30-day window, and the FAA has announced no final determination.

This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.


More from Morning Overview


Morning Overview is reader-supported. Some links in our articles are affiliate links, and we may earn a commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. Full disclosure.