Last night on the local (Austin) news, there was a segment concerning how Capital Metro apparently is planning to raise fares. The reporter was speculating about how large of an impact Capital Metro’s pricing decision might have upon ridership.  However, after studying chapter 2 in ECO 5315, we are in a much better position than the reporter was to predict what will likely happen.  Since we know that the price elasticity of demand for public transportation is quite low (about -0.3 in the United States, according to the textbook (see p. 38)), the increase in price should reduce overall ridership, but not by nearly as much in percentage terms as the increase in the fare. Furthermore, since market demand will decrease in response to an increase in fares, so will overall system costs, assuming that Capital Metro managers not only have the good sense to scale back costs in response to a decline in market demand, but also have the flexibility (particularly from a labor contract and labor relations viewpoint) to do so. The “good” news (from a taxpayer viewpoint, anyway) is that the net effect will be that Capital Metro’s “fare recovery ratio”, or FRR (which measures the percentage of the bus route’s cost that is paid by riders rather than taxpayers) should increase. According to a 2007 Capital Metro report (see, its FRR was just 9% in 2007. Out of 32 North American public transportation systems referenced at, this is by far and away the worst FRR performance; the average FRR for this group is nearly 40%, and the standard deviation is 18%, which implies that Capital Metro is, in every sense of the term, a true “statistical outlier”.

Share →

Leave a Reply

Your email address will not be published. Required fields are marked *

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop us a note so we can take care of it!

Visit our friends!

A few highly recommended friends...


    All entries, chronologically...

    Set your Twitter account name in your settings to use the TwitterBar Section.