Moving the crossover would've helped a little, but not too much. A normal overlap interval for a local event is around 25 seconds. We were at 30 for most cars yesteraday, so with our 3 runs and 149 drivers (160 reg'd, 149 with times) that would've bought us a little less than 40 minutes over the day. Not insignificant, but not the real source of the trouble. The course length doesn't have any effect on how long an event runs other than the time it takes you to walk it and a few extra minutes to get your workers at their stations

. It's all about the interval you can send cars. The course can be 250 seconds, and as long it's laid out so you can send a car every 25 seconds you can still hustle the same amount of competitors through as a shorter course with a similar interval.
Split day works fantastic if there's enough people, but we haven't figured out how to pull it off with the numbers we have. We looked at it hard in the off season, and our numbers aren't big enough (yet) to make it work safely and consistently. We averaged 135 per event last year.
There's another option to get the event moving in a situation like this. The old faithful stopwatch method is advocated by a few of the BOD members. Obviously not the preferred method, but it could've got us going sooner. So the question is, would you rather have one (or a couple) of your times done by stopwatch while we get another timer system in place, or wait?