The Cedar St. number
nobody calculated

The Draft MND and its traffic and evacuation appendices never calculate how long it takes to evacuate Cedar Street — the street the project names as its main way in and out. Appendix I times North Ventura Avenue. Appendix H1 checks ordinary peak-hour traffic. Neither answers how long Cedar itself takes to empty.

This model fills that gap using the applicant’s own inputs: their project vehicle counts (194 at 1 PM, 291 at 9 PM, 303 overnight) and their published 20% / 20% / 60% split to School Canyon, Willett and Seneca, with the School Canyon gate open at minute zero.

Every case was run 1,500 times in a Monte Carlo queueing model of the three Cedar intersections. It is a screening estimate by a resident, not a certified traffic study — and a City analysis should replace it.

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.
—

Median Cedar clearance
—min
Slower 1 run in 10 (P90)
—min
Project vehicles entering Cedar
—
Continue through to Seneca
—
Project queue at Cedar/Alabama
—
Standing length of that queue
—
Queue beyond the 142 ft of public Cedar St — stored inside the project
—
Test the conditions
Project demand — Appendix I
Cedar junction throughput — veh/hr
Held fixed in this panel: 1.74 existing vehicles per household (82 vehicles from 47 mapped households), 15-minute departure window, School Canyon gate open at minute zero. Each of those is tested separately below.
The fire side of the record — Appendix K

The applicant’s Fire Scenario 1 reports a 580 ft/min rate of spread, 54.8-ft flame length and 2.7-mile spotting distance. As a constant-rate unit conversion, 580 ft/min is about 9.1 minutes per mile.

That is not a prediction of when a fire arrives — real spread depends on fuel, slope, wind, spotting and suppression. The point is that the Draft MND never places these fire-behavior outputs beside a Cedar-specific evacuation time. It should.

Reading these numbers

Median Cedar clearance is the time at which the last project vehicle clears its local branch — Cedar to Alabama for the Willett share, Cedar through Alabama, Chickasaw and Seneca for the Seneca share — with existing neighborhood traffic competing for the same junctions. It is not the time to reach safety, and it stops before North Ventura Avenue.

P90 is the slower one run in ten under the same assumptions.

Project queue at Cedar/Alabama counts only project vehicles waiting at the first junction. Existing residents’ cars add to the contention but are not in this count.

Standing length converts that queue at 25 ft per stopped car. Only 142 ft of Cedar — about five cars — lies between the project boundary and Alabama. If the queue is contiguous, everything past that has to stand on the project’s own internal streets.

Junction throughput is the one number that moves the answer most, and nobody has measured it. 600–950 veh/hr are sensitivity rates, not claimed Cedar capacities.

Step 1 — what the record analyzes, and what it doesn’t

Appendices H1, I and K

Every project document identifies Cedar Street as the main local access. Appendix K says the project’s main ingress and egress will be from Cedar Street, extending south to Seneca. Yet the dedicated evacuation analysis only calculates travel times on North Ventura Avenue.

DocumentWhat it analyzesWhat remains missing
Appendix H1 — Traffic Impact StudyOrdinary peak-hour intersection operations; earlier emergency evaluation on N. Ventura AveNo Cedar evacuation clearance time
Appendix I — Evacuation AnalysisN. Ventura Ave north and south of Seneca; project distribution 20/20/60No project-driveway-to-Seneca Cedar clearance calculation
Appendix K — Fire Protection PlanFire behavior; project fire access; School Canyon EVA gateNo direct comparison of Cedar clearance with modeled fire behavior
The Draft MND calculates evacuation time on North Ventura Avenue, but does not calculate Cedar Street clearance under evacuation demand.

Step 2 — the applicant’s published routing

Appendix I, p. 18

Appendix I sends project evacuation traffic to three exits: 20% School Canyon Road, 20% Willett Street, 60% Seneca Street. With the gate open, 80% of project traffic enters Cedar and 60% continues through all three Cedar intersections.

VELLO RETREAT — project demand 100%
  ├── 20% → School Canyon EVA gate → N. Ventura Ave (does not enter Cedar if the gate is open)
  │
  ▼  80% enters Cedar St — 142 ft of public street
══ J1 · CEDAR / ALABAMA ══  ◄ existing neighborhood traffic joins
  ├── 20% → Willett branch (leaves the local model; one-way controls not penalized)
  ▼  60%
══ J2 · CEDAR / CHICKASAW ══
  ▼  60%
══ J3 · CEDAR / SENECA ══
  ▼
══ N. VENTURA AVE ══ regional analysis — Appendix I, not this model
ScenarioProject demandSchool Canyon 20%Willett 20%Seneca 60%Entering Cedar
1 PM1943939116155
9 PM2915858175233
Overnight3036161181242
Project demand from Appendix I Exhibit 6 / Appendix A; split from Appendix I p. 18. Appendix I spells the street “Willet.” The overnight case is rounded to 61/61/181 so the total stays 303.

Step 3 — results

1,500 replications per cell

Median project-vehicle clearance by project demand and junction throughput. The highlighted cell follows the controls above. Across every condition tested, the median runs from about 16 to 33 minutes.

Project demand600 veh/hr750 veh/hr900 veh/hr950 veh/hr
Median / P90 project clearance in minutes. 1.74 existing vehicles per household, 15-minute uniform departure window, School Canyon open at minute zero.
Physical queue-storage check
ScenarioMedian project queueStanding lengthBeyond 142-ft Cedar segment
1 PM / 750 veh/hr34 veh850 ft~708 ft
9 PM / 750 veh/hr93 veh2,325 ft~2,183 ft
Overnight / 750 veh/hr100 veh2,500 ft~2,358 ft
9 PM / 600 veh/hr121 veh3,025 ft~2,883 ft
Overnight / 600 veh/hr128 veh3,200 ft~3,058 ft
9 PM / 750 — all existing traffic moved below Alabama47 veh1,175 ft~1,033 ft
Project vehicles only, at 25 ft per stopped car. The last row is the most project-favorable placement tested: moving all 82 existing vehicles downstream of Alabama lowers median clearance from 26.13 to 23.10 minutes and still leaves 47 project vehicles queued.
Existing-household vehicle demand
CaseVeh / hhVehiclesMedianP90
Appendix H1 rate1.507125.2631.15
Carr Fire lower bound1.748226.1331.82
Local survey2.009427.0833.03
9 PM, 750 veh/hr, 47 mapped households. All-local clearance runs 0.04–0.05 min behind project clearance in each case (25.31 / 26.17 / 27.13).
School Canyon gate delay
Gate opensGate usersInto CedarMedianP90
Minute 05823326.1331.82
Minute 53925227.9533.86
Minute 101927229.3435.75
Minute 15029130.6437.22
9 PM, 750 veh/hr. Vehicles ready before the gate opens are redirected 1:3 to Willett/Seneca — a sensitivity assumption, not an adopted operating plan.
Departure window
WindowMedianP90All-traffic queue at J1
Instantaneous26.1231.94315 veh
15 minutes26.1331.82127 veh
30 minutes30.3432.5610 veh
A slower, staged departure shrinks the queue but does not finish sooner — the 30-minute case simply tracks the last departures.
Convergence check
ReplicationsMedianP90Queue
50026.2932.5893 veh
1,50026.1331.8293 veh
5,00026.1531.8294 veh
9 PM, 750 veh/hr. Sampling variation is small next to the uncertainty in the physical inputs.

Step 4 — what the model shows

Five findings
Finding 1 — Cedar takes roughly 26 minutes to clear, and the range is wide

In the central case — 9 PM demand, 750 veh/hr junction throughput, 1.74 vehicles per household, gate open — median clearance is 26.13 minutes and the slower one run in ten is 31.82 minutes. Across every condition tested, the median ranges from about 16 to 33 minutes. That is the local Cedar number alone, before anyone reaches North Ventura Avenue.

Finding 2 — the queue does not fit on the street

The central case leaves 93 project vehicles waiting at Cedar/Alabama. At 25 ft per stopped car, that is 2,325 ft of traffic. Only 142 ft of Cedar — about five car lengths — lies between the project boundary and Alabama. As a contiguous single-lane queue, the remaining 2,183 ft would have to stand on the project’s internal streets, the same streets fire apparatus would need.

Even the most project-favorable assumption tested — moving every existing neighborhood vehicle below Alabama, even though that overstates the relief — still leaves 47 vehicles, about 1,175 ft.

Finding 3 — the answer turns on a number nobody has measured

Moving Cedar junction throughput from 950 to 600 veh/hr moves median clearance at 9 PM from 20.68 to 32.64 minutes; overnight, from 21.14 to 33.39. No field measurement or capacity analysis of Cedar under evacuation demand appears anywhere in the record. The largest uncertainty is not Monte Carlo sampling error — it is this physical input, and how many existing vehicles use each Cedar segment.

Finding 4 — the School Canyon gate is doing real work, and nobody says when it opens

Appendix I credits School Canyon with 20% of project traffic. If the gate isn’t open when those residents are ready to leave and they redirect onto the other published routes, more of the project enters Cedar: a 15-minute delay puts all 291 vehicles on Cedar and pushes median clearance to 30.64 minutes (P90 37.22). The record should say who or what opens the gate, and how long after an evacuation order civilians can actually use it.

Finding 5 — the three routes relieve Cedar, but they all end on North Ventura

With the gate open, only 80% of project demand enters Cedar and only 60% continues south of Alabama — at 9 PM, 233 and 175 vehicles. But School Canyon, Willett and Seneca all feed the same southbound North Ventura system. Appendix I’s own unmanaged “Worst Case Scenario” south of Seneca already runs over four hours:

Appendix I, unmanaged caseWithout projectWith projectIncrement
1 PM — south of Seneca248.49 min266.92 min~18 min
9 PM — south of Seneca247.35 min274.99 min~28 min
Appendix I Exhibits 20–21: simultaneous evacuation of all zones, no advance notice, no traffic control. Exhibit 22 reports the officer-controlled sensitivity separately as +7 min (1 PM) and +10 min (9 PM). These are Appendix I figures, not outputs of this model.

The local and regional questions should stay distinct — but linked. School Canyon and Willett reduce the number of project vehicles on Cedar. They do not create a new regional arterial.

Appendix I calculation questions

Appendix I page 30 defines capacity as C = N × s × g, and Exhibits 20–21 show 1,700 vphpl (1 lane), a 37.16% green-time value and an adjusted capacity of 631.653 veh/hr. But 0.14 ÷ 0.371 is about 37.7%, not 37.16% — possibly unrounded V/C values. The consultant should identify them, the number of southbound lanes, and the basis for the effective-green figure.

Appendix I also disagrees with itself at 9 PM: the page 33 narrative states an 18-minute project increment north of Seneca, while Exhibit 21 shows about 99 minutes without the project and 110 with it, and Exhibit 22 reports +11 minutes. And the overnight period, when project demand peaks at 303 vehicles, was never analyzed at all.

Questions requiring individual response

14 questions

Each is written so it can be answered separately in the response-to-comments matrix. Borrow any of them for your own comment letter.

  1. 1. Cedar clearance timeWhat is the evacuation clearance time for Cedar Street from the project driveway through the existing neighborhood to Seneca Street under the same 1 PM, 9 PM and overnight project-demand conditions shown in Appendix I? If the City or GTS has already calculated it, please identify the document, assumptions and page.
  2. 2. Existing-neighborhood evacuation demandHow many existing households and evacuation vehicles does the City assume feed Cedar/Alabama, Cedar/Chickasaw and Cedar/Seneca during the project evacuation scenarios? What data source and route assignment support those values?
  3. 3. Cedar geometry and parkingThis model’s central 9 PM / 750 veh/hr case produces a median project queue of 93 vehicles at Cedar/Alabama, about 2,325 ft. Only 142 ft lies between the project boundary and Alabama. What roadway width, on-street parking condition, lane availability and internal queue-storage path does the City assume, and how is emergency-apparatus access maintained while that queue is present?
  4. 4. Effective Cedar junction throughputWhat sustained evacuation discharge rate or saturation headway does the City consider appropriate at Cedar/Alabama, Cedar/Chickasaw and Cedar/Seneca, and what field measurement, HCM/Synchro analysis or other calibration supports each value?
  5. 5. Willett routeDoes Appendix I’s 20% Willett assignment use Cedar → Alabama and then the westbound local street system to Willett → North Ventura Avenue? If so, what capacity and queue-storage assumptions were applied, including posted one-way controls, and where are they documented?
  6. 6. School Canyon gate timingWhat elapsed time from an evacuation order is assumed before the School Canyon EVA gate is open and usable for civilian egress? Who or what opens it, and what evacuation result applies if the 20% diversion credited by Appendix I is delayed or unavailable?
  7. 7. Gate configurationWhat is the approved unobstructed clear opening of the School Canyon EVA gate, and where is the drawing showing the opening, operator, backup power, emergency controls and concurrent ingress/egress geometry?
  8. 8. Three entries onto North VenturaHow does the City evaluate the combined effect of project traffic entering southbound North Ventura Avenue at School Canyon, Willett and Seneca, when the General Plan emergency-evacuation analysis identifies constrained conditions on the downstream North Ventura corridor?
  9. 9. Appendix I capacity calculationFor Exhibits 20 and 21, what number of southbound lanes was used in C = N × s × g; is 631.653 veh/hr a total segment capacity or a per-lane value; what unrounded V/C values were used; and what is the basis for the 37.16% effective-green calculation?
  10. 10. Operational traffic controlAppendix I reports substantially shorter evacuation times when a law-enforcement officer controls Ventura/Seneca and the two-way left-turn lane is converted to southbound travel. Are those measures required by an enforceable condition, mitigation measure or adopted plan? Who implements them, and what result does the City rely on if they aren’t available during an actual wildfire?
  11. 11. 9 PM inconsistencyWhich 9 PM north-of-Seneca project increment is correct: the 18 minutes in the page 33 narrative, or the approximately 11 minutes shown by Exhibits 21 and 22? Please correct the final document accordingly.
  12. 12. Overnight demandAppendix I shows project residential demand of 303 vehicles from midnight through 4 AM, higher than both modeled hours. What are the evacuation travel times using that overnight demand, and why was the maximum-demand period not analyzed?
  13. 13. Fire behavior / evacuation comparisonHow does the City evaluate Appendix K Scenario 1 fire-behavior outputs, including a 580 ft/min rate of spread and 2.7-mile spotting potential, alongside Appendix I evacuation clearance times and any Cedar-specific clearance analysis?
  14. 14. Environmental conclusionAfter addressing the local-route, gate, demand and capacity questions above, what evidence supports the Draft MND conclusion that the project would not impair implementation of an emergency response or evacuation plan, and that wildfire evacuation impacts are less than significant?

Method, assumptions and limits

For the record
InputTreatmentBasis / interpretation
Project demand194 at 1 PM; 291 at 9 PM; 303 overnightAppendix I Exhibit 6 / Appendix A
Project routing20% School Canyon / 20% Willett / 60% SenecaAppendix I p. 18
Mapped existing local households47 householdsResident field mapping, September 2026
Existing vehicles per household1.50 / 1.74 / 2.00 sensitivity1.50 matches the Appendix H1 emergency assumption; 1.74 is a resident-derived lower bound from Carr Fire personal-vehicle mode shares (Wong et al. 2020); 2.00 is a local-observation sensitivity from resident reports and is not treated as statistically representative
Departure windowUniform over 15 minutes in primary caseInstantaneous and 30-minute sensitivities also tested
Cedar control pointsAlabama, Chickasaw, Seneca represented separatelyThree unsignalized intersections listed in Appendix H1
Service-rate sensitivity600 / 750 / 900 / 950 veh/hr at each Cedar control pointSensitivity range only; no value is claimed as measured Cedar evacuation capacity
Run-to-run headway variationCV 0.18 independently at each control pointMonte Carlo sensitivity around the selected mean service rate
School Canyon gateAvailable at minute 0 in primary caseDelay sensitivities at 5, 10 and 15 minutes
Willett / School Canyon after local exitUnconstrained in resident local modelProject-favorable omission; downstream travel is not modeled here
Spillback / crashes / apparatus counterflowNot modeledProject-favorable omission; results are not a worst-case prediction
Standing queue-space conversion25 ft / vehicleScreening conversion used only to translate simulated queue counts into linear storage
Project boundary to Alabama142 ftResident field measurement; about five full 25-ft standing-vehicle spaces
Replications1,500 per cell, seed base 20260917Central case repeated at 500 and 5,000 to confirm convergence
Existing traffic: all 47 households’ vehicles are placed upstream of Alabama in the base case, even though no existing dwellings front Cedar north of Alabama. This is a deliberate upper-bound contention assumption; the placement sensitivity above shows its effect (about 3 minutes in the central case).
What this is, and what it is not

This is a screening model prepared by a resident, not a certified traffic or evacuation study. It is a Monte Carlo queueing model of the local Cedar corridor — not a traffic microsimulation — built to test whether local clearance is materially sensitive to reasonable changes in demand, junction service and gate timing.

  • The 47-household count is resident-mapped; there is no verified household-by-junction route map.
  • The 600–950 veh/hr values are sensitivity rates, not measured capacities of the Cedar intersections.
  • The 2.00 vehicles-per-household case rests on a small, self-selected neighborhood sample.
  • No capacity penalties are applied for smoke, fire apparatus counterflow, disabled vehicles, collisions, trailers, pedestrians or emergency lane closures.
  • Willett is treated as unconstrained after Alabama, and School Canyon as unconstrained after the gate — both favor shorter clearance.
  • The model does not reproduce the full Zone 1 + Zone 4 network; North Ventura figures on this page come from Appendix I.

These limits are why this model should not be used to declare a precise real-world evacuation time — and why a calibrated, Cedar-specific City analysis would give the Planning Commission the missing local number. This model identifies and bounds that missing calculation. It does not replace professional evacuation engineering.

What would resolve the uncertainty
  • A project-specific Cedar evacuation clearance calculation using the applicant’s 1 PM, 9 PM and overnight demand.
  • Verified existing-household route assignment and evacuation vehicle demand for the local Cedar feeders.
  • Measured or calibrated sustained discharge rates for Cedar/Alabama, Cedar/Chickasaw and Cedar/Seneca under evacuation conditions.
  • An explicit School Canyon gate opening and operation assumption, with a sensitivity if the gate is delayed or unavailable.
  • A clear separation between local Cedar clearance and the downstream North Ventura calculation, linked rather than conflated.
  • Identification of any evacuation traffic-control measures relied upon, whether they are enforceable, and who implements them.