Close. It’s the Fairfield/Bridgeport line, with 27A being the start of Route 8, as was also mentioned upthread.
The point I was making was that you usually see letters in related exits. 32N and 32S for route 32 north and south, for example. But these exits are pretty much completely unrelated to each other, and would make giving them the same number with distinctive letters confusing.
Basically, mileage numbering works great when exits are far apart. When they are bunched together, sequential is much better.
But no matter what the situation, mileage exit numbers are indeed difficult to remember. That’s a big negative, IMO. I hate it when I get directions and the person says “I don’t remember the exact number, but…” This never seems to happen with sequentially numbered exits.
That’s true… I spent eight years at a certain exit number off of I-696. I have no idea what the exit number is. Since I’ve moved, there are two exits off of I-94 I regularly use to get home, and two more to get the work. No idea what they are. But when I say things like “Oakwood” or “Gratiot” no one has any problems understanding which exit. All the same, when travelling someplace unknown (like getting through Phoenix), I always like to know the exit numbers.
The only exits I do know for certain are in Michigan; I-75 exit 69 is Big Beaver Rd., and I-75 exit 168 is Beaver Rd. Hey, sorry, certain things stick.
Really? I never use exit numbers when giving directions. I find it much easier to use the name – take the exit for I-70 eastbound toward Columbus – that tells you a lot more than an exit number would. I never remember any exit numbers, whether they’re sequential or mileage-based.
