One Beta Aircraft Reached Salt Lake City. Another Started a Shuttle in Louisiana.

N401NZ left San Diego and landed at Salt Lake City International on September 30. N214BT left North Carolina, crossed the Gulf states, and flew Baton Rouge to Houma and back three times in two days, minting the first corridor identifier in Louisiana. No score moved. California signed its second air mobility law, and the three California watch badges Issue 25 flagged were reset.

Issue 25 asked whether the San Diego transit was over. It was not. N401NZ flew local sorties at Miramar for four days, then turned northeast across the Mojave and the Colorado River and climbed through southern Utah, one 42 to 106 mile leg at a time, until it reached Salt Lake City on the last day of September. That is only the second eVTOL flight the ledger has ever recorded at a Salt Lake City market endpoint, and the first in eighteen months. The same week the North Carolina aircraft went the other way, south through South Carolina and Georgia to the Gulf coast, and then did something a transit does not do: it flew the same 73 mile pair six times. Nobody announced either one. Both are in the ledger because the aircraft broadcast, and both are laid out below, along with a new free tool for hospital and EMS teams, a correction to our own prediction record, and a state bill our news layer filed as a law it is not.

What Changed Since Issue 25

Six developments this week, ranked by what the platform can independently verify. Observed means the aircraft broadcast and the ledger holds the track. Enacted means a signed law on the official record. Published means an audited change to a public record.

San Diego to Salt Lake City

N401NZ stayed at Miramar after Issue 25 went out. The ledger holds a 41 mile local sortie there on September 24 and local flights on September 24, 25, 26, and 27. On September 27 it flew Miramar to Ramona, 18 miles. None of the San Diego pairs repeated, so the market still has no corridor identifier: a transit, not a program.

On September 28 it left. Ramona to Twentynine Palms, 94 miles; Twentynine Palms to Laughlin on the Colorado River, 106; Laughlin to Boulder City, Nevada, 57. On September 29, Boulder City to St George, Utah, 106; St George to Cedar City, 51; Cedar City to Fillmore, 96; a local flight at Fillmore; Fillmore to Provo, 94. On September 30, Provo to Salt Lake City International, 42 miles. Eight cross field legs in three days, every one inside the shape this aircraft has flown since it left Vancouver in August. St George to Cedar City crossed the two day line this week and carries an identifier; the rest are single day legs.

Salt Lake City scores 49 and did not move; the observed ledger does not feed the score. Its market watch moved from stable to developing on October 1 on news activity, not on the flight. The ledger has recorded an eVTOL at a Salt Lake City market endpoint twice: N916LF from Delta to Salt Lake City in March 2025, and this. Beta has said nothing about Utah, and nothing in our news record mentions it.

The Louisiana Shuttle

Issue 25 ended with N214BT flying a repeating pattern between Raleigh, Greenville, and the Outer Banks that Beta announced on September 23. On September 25 it left North Carolina from Florence, South Carolina: Florence to Orangeburg, 82 miles; Orangeburg to Augusta, 64; Augusta to Macon, 108; Macon to Albany, 86. On September 26 it worked west along the Gulf coast: Albany to Dothan, Dothan to Bob Sikes in Crestview, Crestview to Fairhope, and Fairhope to Gulfport, 71 to 84 miles a leg. On September 27, Gulfport to New Orleans Lakefront, 63 miles, and Lakefront to Houma, 50.

Then it stopped moving on. On September 28 it flew Houma to Baton Rouge Metropolitan and back, 73 miles each way. On September 29 it did it twice more. Six legs, two days, one pair, and on September 29 the pair crossed the two day line and received an identifier. It is the first corridor the ledger has recorded in Louisiana. A transit is a chain of single day legs; a shuttle on one pair is what the North Carolina program looked like in its first week. Houma is a base for Gulf of Mexico offshore operations; the ledger does not say why the aircraft is there, and it does not need to.

Louisiana is not a tracked market, and our news record holds no announcement about it. In North Carolina the ledger saw the program six days before the press release. Whether that happens twice is next week's question.

California's Second Law, and a Watch That Held

Governor Newsom signed AB 431 on September 27. It requires Caltrans to include advanced air mobility in the next California Transportation Plan prepared after January 1, 2027, and to form a statewide working group with the Transportation Agency, the Energy Commission, the Air Resources Board, GO-Biz, and the Office of Land Use and Climate Innovation. It creates no vertiport standards, no permitting process, no local zoning duty, and no funding, and it says in terms that it does not interfere with federal airspace authority. Together with SB 800 in 2023, California now has two air mobility laws, both about planning.

Issue 25 said the three California positive watch badges came from a drone statute and would be reset. They were, on September 25, back to developing with an analyst note, and the rule that let a drone restriction pass as an air mobility signal was tightened the same day. AB 431 arrived two days later. The three watches stayed at developing. Nothing in the scores moved either: California's legislation input already counted SB 800, and a planning law is not an operating permission.

For Hospital and EMS Teams

Nearly half of the country's open FAA-registered heliports serve a hospital, and they are the landing sites a medical helicopter or a future eVTOL would use first. Hospital Helipad Check, free and open at airindex.io/helipad-check, finds a pad by the hospital's own name, its health system, or its city, rather than the FAA's abbreviated record name. Each page answers the questions a hospital team asks: whether the FAA record is right, what the FAA has said about the airspace, what cranes and buildings have been filed nearby in the last year, where the nearest alternate landing sites are, and how to correct the record through the FAA's own portal.

Building it meant linking pads to hospitals across the country, which until this week covered five states. 2,769 FAA landing sites are now linked to the hospital they serve, after a review that removed 142 office, government, and business pads that had picked up a nearby clinic's name. One example of what the pages show: Broward Health Medical Center in the Miami market, a level I trauma center, has had 20 FAA obstruction filings within a mile of its pad in the last twelve months. None of it is for navigation, and every page says so.

A Correction to Our Prediction Ledger

Our prediction ledger records an outcome when a real event lands, and four of those outcomes were wrong. A news story about Archer's planned vertiport at L.A. Live had been recorded as Archer beginning commercial operations, and it marked a Los Angeles call as correct; that call is open again. A Phoenix call that predicted Arizona SB 1457 would become law had been marked correct by a different bill, a drone measure; SB 1457 was vetoed on June 19, so the call is now marked wrong. Two public calls, Tampa and Miami, had been validated by regulatory posture records that a September review withdrew because they rested on state actions rather than city ones; both are now marked wrong.

The cause was a rule that turned a press story's tag into an outcome. It now requires a verified event, and 26 outcome records, most of them drawn from unverified press, were withdrawn with the reason kept on file. Nothing was deleted. The market level track record is lower for it, and accurate.

Observed, Confirmed, Announced

Archer, observed. N703AX flew eight local flights at Salinas on six days between September 25 and 30. Nothing south of Salinas yet.

Joby, observed. One local flight by N541JX at Marina on September 30. Nothing in Texas since September 13.

Beta in Vermont. N916LF, N889CD, and N336MR flew 20 flights between Burlington, Plattsburgh, and Rutland, the home pattern behind Burlington to Plattsburgh, the ledger's longest running corridor, flown on 106 separate days.

Introduced, not enacted. New Jersey S4640, introduced on September 28 and scheduled for a Senate Transportation Committee hearing on October 1, would require the state to confirm a heliport or helipad complies with municipal zoning before it issues or renews the facility's license. Our news layer filed it this week as a new law. It is a bill, and it is recorded here as one.

The gate. Seven items sit at the gate this morning and twelve were held back this week. The two most significant tracks of the week, Salt Lake City and Louisiana, have no announcement behind them in our record.

The Weekly Operating Board

Observed flights cover September 24 through September 30 as the ledger stood this morning; October 1 had not yet backfilled. Counts backfill for about a day, and the prior week now reads higher than it did when published.

The standing caveat applies. Observed flight is a floor, never a census. Experimental aircraft may legally fly without broadcasting, and a missing track is recorded as unobserved, never as proof an aircraft did not fly.

Markets to Watch This Week

Top three by predictive significance, from the AirIndex Forward Signals pipeline as of October 2. This ranking leans on the volume of signals a market draws, and volume is attention more than readiness; read the signal counts with that in mind.

See full ranked digest →

What to Watch Next Week

• Where N401NZ goes from Salt Lake City. A second day on any Salt Lake City pair would mint the market's first corridor identifier; a leg out would say the transit continues.
• Whether the Baton Rouge to Houma shuttle runs a third day, and whether anyone announces it. In North Carolina the announcement came six days after the ledger saw the program.
• Ohio's HB 251 takes effect around October 6. It brings vertiports into the state's aeronautics law and requires a state certificate of approval before a vertiport is used commercially.
• A data correction to the legislative momentum input behind the Industry Pulse. A parsing fix found enacted state bills recorded as introduced; it lands with the October 3 refresh, and the one market level effect, Georgia, will be reported next week.

UAM Market Pulse is a weekly intelligence digest from AirIndex. Observed flights come from the AirIndex eVTOL movement ledger, built on FAA registry data and public ADS-B broadcasts. Forward signals are derived from the AirIndex Forward Signals pipeline aggregating classifier outputs, MarketWatch trajectory, and predevelopment facility milestones.

AirIndex · UAM Market Readiness Intelligence · airindex.io