The fire arrives
before Cedar St. clears

Our software model tested how long it takes traffic to get down Cedar Street, turn right on Seneca, and onto Ventura Avenue — both with and without the proposed 117-home Vello Retreat project.

Cedar’s narrow 13-foot-2-inch passageway, with cars parked on each side, is where Vello Retreat’s 200-plus vehicles would merge into our evacuation route. Ventura Avenue is the final bottleneck, where all Zone 1 traffic must merge.

The model tested 96 different evacuation conditions, running each one 250 times to account for normal variations in warning time, visibility, vehicles per household, driver behavior and downstream conditions along Seneca St. and Ventura Ave.

Overhead illustration of Cedar Street in gridlock during an evacuation: a solid double line of stopped cars fills Cedar between Alabama St and Chickasaw St, with both intersections marked BLOCKED and queued traffic backed up along Alabama and Chickasaw as well.

Fire front arrives in
min
Margin at median
min
Median Cedar clearance
min
P90 under these assumptions
min
Existing neighborhood alone
min
Added by the project
min
Peak queue on Cedar
ft
Seneca buffer fills at
min
Embers reach the neighborhood in
min
Whole catchment — minimum time to pass Ventura Ave
min
3.00 mi
Reading these numbers

Clearance is how long until the last car from our streets reaches Ventura Ave. It is not the time to reach safety — it is only the time to get off the corridor.

Peak queue on Cedar is the longest unbroken line of stopped cars north of Alabama St. Only 142 feet of that — about five cars — is public street between the project's edge and the junction. Everything past the fifth car is standing inside the new development, on the streets fire trucks are supposed to use.

Fire front arrives in now uses the applicant's own fire modelling — 580 ft/min in their northern-exposure scenario. Embers reach the neighborhood in is the number that should worry you more. Appendix K puts spotting at 2.7 miles ahead of the flame front, so a fire three miles out is throwing embers into these streets within about three minutes of the order, while the front itself is still twenty-four minutes away. Roads close, cars stall and spot fires start long before any wall of flame arrives.

Seneca buffer fills at is the moment the half mile of Seneca St runs out of room to hold cars. After that, how fast Cedar empties is decided half a mile away, at Ventura Ave, and nothing done on our own street changes it.

Whole catchment is the bluntest number here: every car that has to pass Ventura Ave, divided by how many that junction can pass in an hour. No queuing, no travel time — the evacuation simply cannot finish sooner than this.

Whole catchment is a different and blunter number: all 653 vehicles that must pass the Ventura Ave junction, divided by what that junction can pass per hour. It is a physical floor with no queuing, no mobilization and no travel time in it — the evacuation cannot possibly finish sooner. Cedar clearance can be shorter than this figure because Cedar's vehicles can get through ahead of the Cameron traffic behind them.

Step 1 — the network, and where it fails

Two bottlenecks, two catchments

Earlier versions of the model stopped at Seneca Street and treated cars that reached it as if they had escaped and were free and clear. They are not. Everything upstream flows down to one junction at Ventura Ave, and the catchment feeding that junction is more than twice the traffic on Cedar.

VELLO RETREAT — 117 units, 204 vehicles
  │
  ▼  Cedar St — 142 ft mouth
══ ALABAMA ST ══  ◄ 36 dwellings
  │  258 ft — THE 13-FOOT THROAT
══ CHICKASAW ST ══  ◄ 27 dwellings
  │  635 ft
══ SENECA / CEDAR ══
  │   ◄◄ CAMERON BYPASS — 195 dwellings, 339 vehicles,
  │      reach Seneca without ever touching Cedar
  ▼  Seneca St — 36 ft, two lanes, half mile, holds ~210 vehicles
══ VENTURA AVE ══ THE OUTLET
ConstraintDwellingsVehiclesWhat passes through it
Cedar St 13-foot throat180314117 project units plus 63 existing dwellings. This is where the project's traffic is added.
Ventura Ave outlet at Seneca375653Everything above, plus 195 dwellings arriving via Cameron. This is where it all has to fit.
Bypassing Seneca entirely2035Reach Ventura Ave by another route; excluded from this model
At 1.74 vehicles per household (2018 Carr Fire evacuee survey). Dwelling counts supplied by a resident, August 2026.

Step 2 — results

250 replications per cell · 96 cells

Median Cedar clearance in minutes, across every combination of visibility and Ventura Ave condition, at the evacuation window and Cedar-at-Seneca setting currently selected above. The number in parentheses is how much of it the project adds.

VisibilityGaps availableHeavy flowNear-capacityGridlocked
Cedar corridor clearance, median of 250 paired replications per project state (500 model executions per cell). Parenthetical is the difference between the with-project and existing-only runs under identical conditions.

Step 3 — what the model shows

Six findings
Finding 1 — the binding constraint is the outlet, not the corridor

Cedar's throat carries 314 vehicles. The Ventura Ave junction carries 653, because 195 dwellings reach Seneca via Cameron without ever touching Cedar. Seneca's two-lane half-mile buffer holds about 210 vehicles — a real cushion, and still not enough. Under gridlocked conditions it fills in roughly 25 minutes, and from that moment Cedar's discharge is governed from a half mile downstream. Every junction-capacity number upstream stops mattering.

Two clearance times are worth keeping separate, and conflating them is the easiest way to misread this analysis. Cedar corridor clearance is the last Cedar-origin vehicle reaching Ventura Ave — the headline figure on this page. Whole-catchment clearance is the last of all 653 vehicles passing the outlet. Under the severe blockage stress test the second is roughly 5.3 hours for the existing neighbourhood alone and 7 hours with the project, and neither figure is the time to reach safety.

This has a consequence that cuts against the project's own proposed mitigations. Relieving Cedar — by removing parking, by opening the School Canyon gate — moves vehicles to the outlet faster without widening it. Parallel paths into a single constrained junction do not add capacity. They change which street the queue stands on.

The two junctions are in series, so only the tighter one governs — and which one that is depends on Ventura Ave. Under night and dense smoke with gaps available on Ventura Ave, tightening the Cedar-at-Seneca right turn from free-flowing to backed-up nearly doubles clearance, from 76 to 134 minutes. Under gridlock the same change moves the result by about thirteen minutes on four hundred — indistinguishable from noise. When the outlet fails, nothing upstream of it is worth fixing. That is worth knowing before anyone proposes striping, signage or parking removal on Cedar as mitigation.

Finding 2 — the neighborhood already has a problem, and the project roughly doubles it

This is the honest reading, and it is worth stating plainly because the applicant will otherwise state half of it. Under Thomas Fire conditions — night, dense smoke, Ventura Ave gridlocked — the 63 existing dwellings that feed Cedar Street take about 2.6 hours to get their last vehicle to Ventura Ave without any project at all, and the full 258-dwelling Seneca catchment takes roughly 5.3 hours to finish passing the outlet. That is not the project's doing.

What the project does is add roughly four hours to that under the same conditions, and between 47 and 61 minutes even when Ventura Ave has gaps. A pre-existing deficiency is not a defense: CEQA cumulative-impact analysis exists precisely for a project that makes an already-significant condition substantially worse. It also bears directly on the finding required to grant a density-bonus incentive — that there is no specific adverse impact on public health and safety for which no feasible mitigation exists. The feasible mitigation is named in the City's own General Plan.

Finding 3 — a slower evacuation is not necessarily a worse one, and that tells you where the constraint is

Spreading departures over thirty minutes instead of fifteen has two opposing effects: it lowers the peak arrival rate, which helps, and it puts the last household on the road fifteen minutes later, which hurts. Which wins is a diagnostic.

When Ventura Ave has gaps, the slower window is 3.5 minutes worse — the corridor was keeping up, so the only thing that changed is that the last vehicle started later. When Ventura Ave is gridlocked, the slower window is 15 minutes better, because peak demand never mattered; the outlet was serving at a fixed rate the whole time and arriving earlier only meant waiting longer.

That asymmetry is worth stating plainly to a decision-maker: under the conditions that matter, warning people sooner does not get them out faster. Earlier warning is valuable — it is simply not a mitigation for an outlet that cannot pass the traffic.

Finding 4 — visibility is not a footnote

Wildfire evacuations happen at night and in smoke. The Thomas Fire reached Ventura after dark. Low visibility reduces junction capacity by roughly 10 to 12 percent in the Highway Capacity Manual's weather adjustments, and darkness compounds it. Moving from daylight and light smoke to night and dense smoke costs the corridor 19 minutes when Ventura Ave has gaps and 68 minutes when it is gridlocked.

Any analysis that models a clear weekday afternoon is modelling the condition under which evacuation is least likely to be needed.

Finding 5 — the City has already modelled this outlet, and found it over capacity

The severe blockage case in this analysis no longer rests on a neighbour's recollection. Appendix B of Ventura's own General Plan — the Emergency Evacuation Analysis prepared by Rincon Consultants in April 2024 under SB 99 and AB 747 — models a wildfire originating in the city's northern hillsides. That is this project's scenario. Its findings for the road this corridor drains onto:

City of Ventura, Appendix BSegmentFinding
Baseline — ordinary Thursday, 5 p.m.N Ventura Ave, Main St to Dakota Dr1.3 mi congested,
0.7 mi over capacity
Northern hillside wildfireN Ventura Ave, Dakota Dr to E Main St2.0 mi over capacity
Seneca St meets Ventura Ave inside the segment the City finds over capacity in both cases. "Over capacity" is the City's own term for a volume-to-capacity ratio above 1.

Two things follow. First, the outlet this neighbourhood depends on is already over capacity on a normal weekday evening, before any fire and before this project. Second, in the City's own wildfire scenario it is over capacity for two miles — and that scenario also lists North Ventura Avenue among its roadway closures north of the fire, concentrating everything southbound.

That allows the outlet capacity to be derived rather than assumed. The City's analysis uses 1,900 vehicles per lane per hour as ideal arterial flow; Ventura Ave is three lanes at Seneca. Applying standard gap-acceptance capacity to a minor-street left turn merging into that flow:

Ventura Ave V/CThrough volumeSeneca left-turn capacity
0.31,710 veh/hr82 veh/hr
0.52,850 veh/hr13 veh/hr
1.0 — the City's finding5,700 veh/hreffectively zero
Gap-acceptance capacity, 6.9 s critical gap and 3.3 s follow-up. Illustrative — no turning-movement counts have been taken at this intersection.

This reverses the direction of the criticism this analysis expected. The 120 veh/hr setting is generous, not pessimistic. It implicitly assumes courtesy gaps or active traffic control. At the volumes the City's own document projects, an unsignalised left turn out of Seneca has no meaningful capacity at all.

The City's evacuation strategy list, in the same appendix, recommends "minimize left-turn movements along evacuation routes and on roads leading to evacuation routes" and establishing traffic control points staffed by emergency management personnel. Neither is proposed for Seneca and Ventura Ave, and nothing in this project provides either.

Finding 6 — the queue stands inside the project's own fire lanes

Only 142 measured feet of Cedar St — five cars — sits between the project boundary and the Alabama St junction. Everything beyond the fifth vehicle stands inside Vello Retreat, on the 26-foot internal streets that must be posted and kept clear as fire apparatus access. Peak queues in this model run 2,975 to 4,375 feet depending on conditions — roughly 2,830 to 4,230 feet of standing traffic inside the development. Without the project the queue north of Alabama is zero feet in every single cell, because no dwellings front that stretch of Cedar.

Cedar itself measures 29 feet 10 inches curb to curb, re-measured on site in September 2026. That is the width of the whole run from Seneca St up to Alabama St — walked end to end, with no narrower section anywhere along it. What matters for an evacuation is not the curb-to-curb figure but what is left to drive through. Where two neighbours park opposite each other — a full-size pickup at 8 ft 6 in and a large van at 8 ft 2 in, both mirror to mirror — the clear travelled way is 13 feet 2 inches.

The California Fire Code sets a 20-foot minimum unobstructed width for required fire apparatus access roads. Whether and how that provision applies to this existing public segment is a determination for the Ventura Fire Department, and one worth asking them to make on the record — the measured condition sits 6 ft 10 in, or 34%, below that floor. At 13 feet 2 inches a Type 1 engine cannot pass a stopped passenger car: it is short by about a foot on the body and three feet mirror to mirror. Title 14 CCR §1273.00 requires roads to serve emergency equipment and civilian evacuation concurrently. Here they cannot.

Method, assumptions and limits

For the record
ParameterValueBasis
Project units117DRC project description. Note that SB 99 defines a single entrance/exit neighbourhood as 30 or more dwelling units with only one route to a collector or arterial, per CFC Appendix D107.1 — a definition this project meets nearly four times over
Vehicles per household1.74 (floor)2018 Carr Wildfire evacuee survey (Wong, Broader, Walker & Shaheen, UC Berkeley, n=284). A floor: the survey caps "three or more" at three and counts towed items separately
Existing dwellings, Cedar corridor638 fronting Cedar, 18 Alabama east, 17 Chickasaw east, 20 west of Cedar. Resident count, August 2026
Existing dwellings, Seneca catchment258278 total in the drainage area less 20 that reach Ventura Ave without passing Seneca. Resident count — the single most consequential input in this model and the one most in need of independent verification
Cedar St geometryMeasuredProperty line to Alabama 142 ft; Alabama to Chickasaw 258 ft; Chickasaw to Seneca 635 ft; Seneca to Ventura Ave ~half mile. 29 ft 10 in curb-to-curb (re-measured September 2026, superseding an earlier 26 ft figure), continuous from Seneca to Alabama with no narrower section; 13 ft 2 in clear where a full-size pickup and a large van park opposite each other. Widens to roughly 40 ft about 26 ft north of Hupa St — a step change, not a taper
Seneca St36 ft, 2 lanesMeasured curb to curb; ~23 ft clear with parking both sides. Storage of ~210 vehicles assumes both lanes are used for outbound queue — half a mile at 25 ft per vehicle. If one lane is held open for apparatus ingress, as Title 14 §1273.00's concurrency requirement implies, storage is ~105. Tested: this changes when Seneca fills (40 min → 22 min under the stress test) but moves clearance by under a minute, because storage does not change throughput
Cedar junction capacity600 veh/hrDegraded two-way stop control — 6.0 s headway. For comparison, the City's Appendix B assumes 950 veh/lane/hr as ideal flow for collector and local roads, so this sits well below the City's own uncongested benchmark. Held fixed here; earlier versions swept 600–1,286
Visibility adjustment1.00 / 0.90 / 0.88 / 0.78Daylight-light / night-light / daylight-dense / night-dense. Sensitivity factors informed by FHWA and HCM low-visibility capacity adjustments — but that published framework is for freeways, and applying it to a low-speed stop-controlled turn is an extrapolation that has not been locally calibrated. The 0.78 night-plus-dense-smoke value is a stress-test factor, not a published intersection factor
Ventura Ave outlet capacity120–900 veh/hrSeneca traffic turns left into one-way southbound flow on Ventura Ave. 900 = gaps readily available. 120 = merging into a stationary queue on courtesy gaps only — this is a severe downstream blockage stress test, not an observed capacity. Independently supported by the City's own General Plan Appendix B (Rincon Consultants, April 2024), which finds North Ventura Ave over capacity from Dakota Dr to East Main St in its northern-hillside wildfire scenario — and over capacity for 0.7 mi at baseline. Gap-acceptance analysis at those volumes gives a left-turn capacity near zero, so 120 veh/hr is a generous stress test. No turning-movement counts have been taken at this intersection
MobilizationLognormal, 15 or 30 minTruncated at the window: "a 30-minute evacuation" means every household has departed by minute 30. Selectable above; 30 minutes is the default as the more realistic case for a 375-dwelling catchment
Fire arrivalAppendix KNow taken from the applicant's own fire behaviour modelling (Draft MND Appendix K, Fire Protection Plan). Scenario 1, northern exposure: 50 mph north/north-east wind, 35% slope, 320° aspect, fuel moistures 2/2/3% with live herbaceous 30% and live woody 45%, fuel model SCAL18 sage-buckwheat at 60% blended with SH5 dry-climate shrub at 40% — giving 580 ft/min rate of spread, 34,180 BTU/ft/s fireline intensity, 54.8 ft flame length and 2.7 miles of spotting. Scenario 2, eastern exposure: 60 mph wind, 10% slope — 366 ft/min, 20,817 BTU/ft/s, 43.6 ft flames, 2.3 mi spotting. A rule-of-thumb option remains for what-ifs. Appendix K also reports 25 ft/min with treated fuels on site — that is the fuel modification zone on the pad, not the untreated hillside the fire crosses to reach it, and 580 ft/min is what governs arrival at the neighbourhood
Replications250 per cell96 cells: 4 visibility × 3 Cedar-at-Seneca × 4 Ventura Ave × 2 evacuation windows, each run with and without the project
What this is, and what it is not

This is a screening-level analysis prepared by a resident, not a certified traffic impact study. It uses a simplified queuing representation rather than a calibrated microsimulation. It does not model route choice beyond the corridor, driver heterogeneity, towed vehicles, pedestrian evacuees, phased zone releases, or active traffic management by police — all of which a real evacuation would involve, some helping and some hurting.

Three inputs carry most of the uncertainty and none of them are the model's engine: the 258-dwelling Seneca catchment, the Ventura Ave gridlock rate, and vehicles per household. Two of the three rest on resident accounts. They should be verified before any of these numbers are relied upon.

This work began before the Draft MND was released. The applicant's Evacuation Analysis (Appendix I, April 2026) has since been published, and it does not reach the question this page was built to ask. It computes clearance times for two segments of North Ventura Avenue, north and south of Seneca. Cedar Street is not a study segment — its entire treatment is one sentence describing the local streets as operating under low traffic conditions. No turning-movement counts have been taken at Seneca and Ventura Ave, the junction this whole catchment must pass through, and no analysis in the record combines the full Seneca catchment with the project at that junction.

Where the two analyses do overlap, they are not far apart. Appendix I uses an effective capacity of 631.65 veh/hr on a three-lane arterial; this model assumes 600 veh/hr at a stop-controlled residential junction. Appendix I derives 194 to 291 project vehicles; this model uses 204. Appendix K, the applicant's fire protection plan, models a rate of spread of 580 ft/min under a 50 mph wind — 6.59 mph, or roughly thirteen percent of wind speed. Its second scenario works out to about seven percent. The ten-percent rule this page previously used sits between them, and the fire-arrival figures now come from Appendix K directly rather than from any rule. Both analyses produce corridor clearance times measured in hours.

The purpose of this page is narrower than prediction: to show that the corridor's evacuation performance is governed by an outlet nobody has analysed, and that this is answerable with arithmetic that is not yet on the record. If a calibrated study reaches different numbers, that study should supersede this one. The point is that one should exist before the Planning Commission acts.