Second Ave. Sagas
  • About
  • Contact Me
  • 2nd Ave. Subway History
  • Search
  • About
  • Contact Me
  • 2nd Ave. Subway History
  • Search
Second Ave. Sagas

News and Views on New York City Transportation

Manhattan

What future the South Ferry station?

by Benjamin Kabak December 18, 2012
written by Benjamin Kabak on December 18, 2012

A glimpse of the South Ferry platform shortly after the Sandy floodwaters receded. (Photo via MTA New York City Transit / David Henly)

To repair the South Ferry subway station to its pre-Sandy condition is going to cost a lot. Some — this author for instance — think it may cost too much to do so. Must we spend $600 million on a station we just spent $540 million to construct less than half a decade ago? Still, the MTA isn’t about to give up on the station, and after releasing a funding request breakdown on Monday, MTA officials had more to say about their plans for South Ferry.

Less than two months after the storm, Transit is still hazy on its future plans for South Ferry. The station is expected to be closed for at least another year, and crews are still assessing its condition. Still, as Transit President Tom Prendergast explained during yesterday’s committee meetings, the station may undergo some changes and some improvements. Ted Mann of The Journal had more:

The MTA had previously estimated that it would cost $600 million to fully rebuild South Ferry and the adjoining Whitehall Street station. For the first time Monday, however, Prendergast signaled that work at South Ferry will not necessarily replicate the exact station that sat at the site before the storm.

If the MTA decides that the cost of repairing some parts of the station “aren’t worth that investment or we could use that money elsewhere, we would make that decision along those lines,” Mr. Prendergast said. The twin challenges of rebuilding versus redesigning facilities to better survive future storms can’t be easily separated, he said.

The MTA is not considering eliminating the South Ferry station or moving its footprint. It was rebuilt and expanded in 2009 at a cost of more than $500 million. But some parts of the complex could conceivably be moved elsewhere. One example: the station included a train-dispatch office for the No. 1 line. Such vulnerable equipment could conceivably be moved out of the way of future floods as the MTA decides how to rebuild, Mr. Prendergast said. “If you get a situation where you say, ‘The likelihood of this flooding occurring again is really, really high,’ would you really put this asset back in the same location?” he said.

Not rebuilding the station isn’t an option, and reopening the old five-car South Ferry loop isn’t on the table either. The feds poured $500 million into its construction the first time around and are seemingly prepared to do the same, if not more, this time. Furthermore, the South Ferry station, due to its proximity to the Staten Island ferry, serves as a vital link to Manhattan’s West Side for commuters. It was the 33rd most heavily trafficked station in 2011.

But at the same time, the new South Ferry had flaws. It was built in a flood zone with few protections from a massive, if unexpected, storm surge, and its waterproofing was deficient before Sandy. The MTA can fix these problems by, as The Journal notes, moving key equipment further down the line and repairing inadequate construction work. Whatever the outcome, it’s going to be at least another year, and that in and of itself is something Transit must work to avoid in the future.

December 18, 2012 65 comments
1 FacebookTwitterPinterestEmail
MTA Construction

For 2013, a wide expansion for Fastrack

by Benjamin Kabak December 17, 2012
written by Benjamin Kabak on December 17, 2012

Due to Hurricane Sandy, the MTA’s new Fastrack program suffered a premature end in 2012. The November treatments were canceled as the MTA worked first to restore subway service and then to repair the transit system. Despite this road bump, Fastrack will be back in 2013, and yesterday, New York City Transit unveiled to me the full schedule of work lined up for the coming year.

In a press release issued Monday, Transit touted the benefits of Fastrack. The overnight subway shutdowns allow MTA workers unimpeded access to subway infrastructure, and repairs and renovations can be completed quickly and without the same fear of passing trains. The agency used some glowing phrases to describe “an increase in productivity and significant decreases in employee accidents and maintenance costs” and cited cost savings — to the tune of $17 million — and reduced delays as reasons for a 2013 return.

“Over the past year we have found this to be an extremely effective way to maintain a subway system that operates around the clock, seven days a week,” NYC Transit President Thomas F. Prendergast said. “We have seen concrete benefits in the way the system is being maintained through FASTRACK and we are now ready to roll it out to other line segments.”

As the 2012 version of Fastrack focused on the system’s core trunk lines in Manhattan and parts of Brooklyn, the new track segments venture further afield into the Bronx, Queens and Upper Manhattan. Still, the MTA assures its customers that these new routes have bend chosen because “there is adequate alternate means of transportation, including enhanced services along some bus lines during work periods.” I’d stick with alternate nearby subway lines over late-night bus service, but that’s just me.

So what are these new corridors? They include the Concourse Line (D) north of 161st St., the BMT Broadway Line (N/Q/R) between Queensboro Plaza and Court Street; the Eighth Avenue Line (A) north of 168th St.; the Queens Boulevard Line (E/F/M/R) between 5th Ave./53rd Street and Roosevelt Avenue; and the East Side IRT (4/5/6) north of Grand Central to 125th St. There will be a few one-offs during the year as well.

Each Fastrack segment will receive four treatments a year when service is shutdown overnight from 10 p.m. to 5 a.m. for four consecutive nights. First up is the D train’s Concourse Line during the week of January 14. That will repeat during the weeks of April 8, July 15 and November 4. The BMT Broadway line will be shutdown during the weeks of January 28, April 15, June 17 and September 30. The A train won’t venture north of 168th St. during the weeks of February 25, June 10, August 26 and November 18. The Queens Boulevard work will occur during the weeks of March 18, June 3, August 12 and October 14. Finally, the 6 train will be offline during the weeks of March 25 and September 9 while the 4 and 5 tracks will be shut down during the weeks of May 20 and October 28.

But! That’s not all. In addition to this trunk line work, there are a few other overnight Fastrack happenings. Out in Brooklyn, between the D train’s Coney Island Creek Bridge and the North Stillwell Interlocking, the MTA will conduct a weekend day-time Fastrack during the weekends of February 2, May 18, September 5 and November 23. Furthermore, a series of one-offs will dot the year. The J train tunnels in Manhattan will undergo maintenance during the week of April 1 while the F train’s Rutgers Tube through to Broadway/Lafayette will be off during the week of December 2. The R train will not run south of 36th St. along 4th Ave. during the week of May 6, and the 2 train will not operate south of Franklin Ave. during the week of January 21. The A/C/D trains will not run from 59th St. to either 168th or 161st St. during the week of September 16.

That’s quite the laundry list of Fastrack, and if you’re eyes haven’t glazed over yet, congratulations. The MTA is clearly engaged in an aggressive attempt at, well, something. It’s a money-saving effort to speed up necessary and vital repairs. It’s a major inconvenience to many late-night commuters who have few alternate routes. It is, as I’ve said before, the new normal, and it’s taking over more and more of the system. It starts up again in just a few weeks, and one day soon, we won’t remember when Fastrack wasn’t a part of the normal way of things. We don’t always like it, but we live with it.

December 17, 2012 31 comments
1 FacebookTwitterPinterestEmail
AsidesService Advisories

R train’s Montague St. Tunnel expected back on Friday

by Benjamin Kabak December 17, 2012
written by Benjamin Kabak on December 17, 2012

New York City Transit expects to restore R train service between Brooklyn and Lower Manhattan this Friday, Carmen Bianco, Senior Vice President of the Department of Subways, said this morning at the MTA Board’s committee hearings. R train service has been suspended between the two boroughs since Hurricane Sandy came ashore, and the Montague St. Tunnel had sustained some of the heaviest damage due to flooding. The news is welcome for interborough commuters who have found the 2/3 and 4/5 lines more crowded than usual with the R out of service.

With this announcement, only the A train’s Rockaway service and the 1 train’s South Ferry terminal remain offline. Bianco today said that he expects regular service to the Rockaways to be restored before South Ferry is operational again. It’s unclear though how long either area will be without regular service as South Ferry sustained heavy damage and no full station assessment has been conducted. Transit officials say they are unclear as to what extent they will restore South Ferry, but it’s possible that some station components will be improved from their pre-Sandy condition.

December 17, 2012 17 comments
1 FacebookTwitterPinterestEmail
MTA ConstructionMTA Economics

Inside the MTA’s $4.7B capital request for Sandy

by Benjamin Kabak December 17, 2012
written by Benjamin Kabak on December 17, 2012

While Service on the R line was restored to Whitehall St., trains are still unable to travel through the Montague Street tube. Signage crews made changes directing all passengers to what is usually the downtown platform for all service. (Photo by MTA New York City Transit / Marc Hermann)

During the MTA Board and Committee meetings this week, the agency will present a detailed breakdown of its request for capital funds to repair the transit system after Hurricane Sandy swept through. Overall, the MTA is asking for $4.755 billion, nearly all of which the agency expects to receive from the federal government and insurance. The MTA is also asking for permission to bond out $950 million should the need arise, but what’s missing from the document speaks nearly as loudly as what’s in it.

In the document — available here as a PDF — the MTA stresses in no uncertain words the need for approval for this money. The addition of nearly $5 billion to the MTA’s capital tab should have no impact on the operating budget, but doing nothing is not an option. “There are no viable alternatives to the proposed action,” the staff summary reads. “Delaying repair work could result in further service delays, increased safety risks, and lower reliability. Further, it is not tenable to substitute existing funds supporting ongoing capital projects for these restoration projects.”

That’s not new, and neither is the MTA’s estimated cost projections. We know South Ferry, for instance, is going to cost $600 million to repair, but now we can see why. The new document contains cost breakdowns, and maybe it makes this price tag a bit easier to swallow. It’s now just $600 million for one station that, a few years ago, cost $540 million to build from scratch. Rather, it’s $600 million for a comprehensive repair of a large station complex and nearly all of the technology within.

According to the PDF, the South Ferry/Whitehall Station costs combined will add up to $600 million. Of that total, $350 million will go toward station repairs, $20 million will go into line equipment repairs, $200 million will go into signal and communications equipment repair, and $30 million will help repair traction power. It seems clear from this breakdown that the $600 million does not include work inside the Montague St. Tunnel. Although there is no line item for the individual tunnels, the total for other signal work reaches $770 million.

No matter how we slice and dice it, it’s still a lot of money, and the bulk of it will go to South Ferry. After all, Whitehall St. is already open and in revenue service. Still, with South Ferry totaled and Whitehall not unscathed, the costs mount. We still need a serious examination of how the MTA spends money and why projects cost so much though before we can be completely satisfied by this price tag. Whether we will get one remains an open question.

But as I said, this document is notable for what it doesn’t have as well. It doesn’t have any details about preventative measures. The MTA wants nearly $5 billion to repair and restore its transit network, but it doesn’t yet know how much it needs to protect the system or what those protections will look like. As two MTA officials said to me during my last Problem Solvers event at the Transit Museum, it’s just too early to know what to do. It’s too close in time to the storm and too many resources are devoted to repair and restoration work.

For now, that’s OK. It’s important in the short term to bring the transit system back to where it was before the end of October, and for now, the MTA should be spending its limited resources on that approach. But that conversation needs to happen. It should happen this week as the MTA’s Finance Committee and full Board assess the funding request. It should happen as repair work moves forward, and it should happen after repairs are completed. The next storm will come, and it can’t cost $5 billion each time.

December 17, 2012 24 comments
1 FacebookTwitterPinterestEmail
Service Advisories

Weekend work impacting four subway lines

by Benjamin Kabak December 15, 2012
written by Benjamin Kabak on December 15, 2012

We’re getting closer to Christmas. Without snow on the ground, it’s still easy to see that as weekend work has slowed to a crawl.


From 12:01 a.m. Saturday, December 15 to 5 a.m. Monday, December 17, Manhattan-bound A trains run local from Broadway Junction to Utica Avenue due to elevator work at Utica Avenue.


From 11:45 p.m. Friday, December 14 to 5 a.m. Monday, December 17, Coney Island-bound D trains skip 167th Street, 161st Street and 155th Street due to track maintenance work at 167th Street.


From 11:45 p.m. Friday, December 14 to 5 a.m. Monday, December 17, R trains operate between Forest Hills-71st Avenue and 34th St and Q trains operate local in both directions on Broadway between Canal Street and 57th St-7th Avenue due to signal work in the Montague Tube and adjoining areas.

December 15, 2012 11 comments
0 FacebookTwitterPinterestEmail
Subway Maps

Google Maps – and transit directions – returns to iOS

by Benjamin Kabak December 13, 2012
written by Benjamin Kabak on December 13, 2012

Courtesy of the Second Ave. Sagas Instagram account comes a screenshot from my iPhone. I awoke on Thursday morning to find that Google Maps — and with it, native in-app integration of transit directions — had returned to Apple’s iOS mobile platform. iPhone and iPad users could once again turn to the market leader in digital mapping and directions.

When Apple announced iOS 6 a few months ago, they made headlines with the decision to torpedo Google Maps in favor of an in-house solution, and the in-house solution was an unqualified disaster. Location searching was inaccurate; directions were wrong; and the lack of transit had many advocates wringing their hands. Google Maps returns transit to the mapping app with a smooth interface to boot.

Writing in The Times on Thursday, David Pogue wrote a glowing review of the new app, and he highlights the public transportation piece:

Along with driving directions, Google Maps gives equal emphasis to walking directions and public transportation options.

This feature is brilliantly done. Google Maps displays a clean, step-by-step timeline of your entire public transportation adventure. If you ask for a route from Westport, Conn., to the Empire State Building, the timeline says: “4:27 pm, Board New Haven train toward Grand Central Terminal.” Then it shows you the names of the actual train stops you’ll pass. Then, “5:47 pm, Grand Central. Get off and walk 2 min.” Then, “5:57 pm, 33rd St: Board the #6 Lexington Avenue Local towards Brooklyn Bridge.” And so on.

Even if public transportation were all it did, Google Maps would be one of the best apps ever. (Apple kicks you over to other companies’ apps for this information.)

It may, of course, strike some as silly to focus so much on a map app on one mobile platform, but iOS is one of the leading platforms. By omitting a native integration of transit into their app, Apple could subtly influence people’s behavior. Google, on the other hand, includes information for around one million public transportation stops, and Google makes it easy to get transit directions. Thus, it encourages transit use. The return of a Google Map application, available in Apple’s App Store, is a welcome one indeed.

December 13, 2012 19 comments
0 FacebookTwitterPinterestEmail
Fare Hikes

In MTA fare hike, a $2.50 base and a $112 30-day card

by Benjamin Kabak December 13, 2012
written by Benjamin Kabak on December 13, 2012

After a series of public hearings last month, MTA Chairman and CEO Joe Lhota has unveiled his recommended fare hike proposal ahead of Wednesday’s board vote. The package of fare hikes across all MTA properties resembles the one discussed Monday and will generate $450 million in additional annual revenue for the agency.

When the dust settled from the public debate, Lhota had determined that across-the-board increases — instead of the usual steep spike in the cost of unlimited ride cards — would be preferable. The base fare will go up to $2.50 with a 5% bonus on all purchase above $5. The 7- and 30-day cards will increase to $30 and $112, a jump of $1 and $8 respectively. “Customers asked us to minimize increases to the passes and maintain some level of bonus,” Lhota explained in a letter to the MTA Board. “They did not want to see another double-digit percentage increase in the 30-day pass.”

In addition to the fare increases, Lhota has also urged the MTA to adopt the $1 surcharge for new MetroCards. The MTA first announced plans to explore such a surcharge back in 2010, but implementation has been delayed due to some technical hurdles. “By encouraging customers to refill their cards,” Lhota wrote, “this fee will realize an estimated $20 million per year, both from savings from card production and new revenue from the fee.” The fee will not apply to out-of-system MetroCard purchases.

Under the new fare structure, the MTA is lowering the break-even point for unlimited ride cards. Currently at 14 rides for a 7-day card and 50 rides fr a 30-day card, the breakeven point will now be at 13 rides and 48 rides, respectively. Even as riders across the board are being asked to shoulder more of the MTA’s fiscal load, unlimited users are not being asked to take on a disproportionate amount of the increase this time around.

The MTA Board will vote on the fare hikes on Wednesday, and we’ll do it all over again in two years when the next schedule rate increases cross our paths.

For more on the fare hikes, check out this comprehensive PDF. Changes to tolls charged by MTA Bridges & Tunnels are documented here.

December 13, 2012 23 comments
0 FacebookTwitterPinterestEmail
AsidesMetroCard

MTA introduces online MetroCard claim system

by Benjamin Kabak December 12, 2012
written by Benjamin Kabak on December 12, 2012

For years, the MTA has offered a protection plan of sorts for MetroCards. For those who buy fare cards with a credit or debit card and find that card lost or stolen, a quick call to 511 can result in an eventual refund. It’s not the speediest process, but it works. Now that process is available online.

As part of an upgrade to the MTA’s eFix website, lost of stolen MetroCards may now be reported online. The site isn’t quite intuitive; a lost or stolen card gets reported via the “Balance Protection claim.” But there it is, a 21st Century solution to a misplaced or misappropriated MetroCard.

December 12, 2012 17 comments
0 FacebookTwitterPinterestEmail
BusesMTA Technology

For the MTA, it’s BusTime vs. Countdown Clocks

by Benjamin Kabak December 12, 2012
written by Benjamin Kabak on December 12, 2012

As we know, New York City buses are slow and unreliable. Delayed by the vagaries of surface traffic, the city’s buses rarely stay on schedule and inch along surface streets. Buses are underutilized and often looked down upon by even their own riders. Few advances in the way we treat buses represent lost opportunities to move New Yorkers quickly and efficiently.

Over the past few years, as bus-tracking technology has swept the globe, New York has slowly embraced it. An expensive pilot program along 34th St. brought proprietary technology and countdown clocks to the heavily-trafficked corridor, but when the MTA searched for a system-wide solution, the agency instead went with a distance-based tracking system and no countdown clocks. BusTime is an open-source solution with flexibility for growth and real cost savings over closed systems.

BusTime, of course, isn’t perfect. It requires the user to possess a smart phone or texting capabilities and actually know that the technology is in place. It is a distance-based system, and for a bus to travel 1.3 miles depends upon the route, the time of day and the traffic in front of it. New Yorkers like to know time in minutes, not miles. (For a succinct summary of the MTA’s failed countdown clock efforts, check out this Daily News overview.)

Now, though, some politicians and advocates aren’t happy. Noting how countdown clocks make subway waits more tolerable and empower riders, they want countdown clocks, and they wait them now. Earlier this week, Council Member Brad Lander announced a new initiative aimed at convincing the MTA to install countdown clocks on bus shelters. Lander is leading the way with a piece of legislation that “calls upon the Metropolitan Transportation Authority, the Department of Transportation, and Cemusa to work together to install bus arrival time displays in bus shelters using data from the MTA’s Bus Time technology.”

Streetsblog had more from the press conference:

With countdown clocks already available in many subway stations, Lander and advocates say bus riders deserve the same convenience, and that not everyone has access to a cell phone or the Internet before catching a bus…Lander’s office estimates that the counters cost between $4,000 and $6,000 to purchase and between $1,000 and $1,600 to maintain each year, based on figures from other cities with bus countdown clocks, including Washington, DC, Boston, Albany and Syracuse.

The MTA has argued that countdown clocks at bus stops provide marginal benefit to riders at relatively high costs, and is focused on rolling out its BusTime program citywide by the end of next year. By that time, Lander would like a plan for bringing countdown clocks to the city’s 3,300 bus shelters. The route to achieving that goal is murky; Lander introduced the resolution to start the discussion.

Lander said that, ideally, revenue from advertising on countdown screens would fund the installation and maintenance of the clocks. If advertising could not cover all costs, he suggested they could be borne in part by Business Improvement Districts, council member discretionary funds or other local partners interested in bringing clocks to their areas. Lander added that bus countdown clocks were a popular idea during the last round of participatory budgeting in his district.

I have a simple challenge for Brad Lander: He feels it will cost up to $20 million to install countdown clocks that can use the BusTime API to pull data (although reliably converting distance to time is another issue). He believes it will cost around $5.28 million for maintenance each year. Instead of passing a symbolic resolution urging a solution, simply find a way to pay for the clocks. The $20 million outlay is hardly a huge expense, but it’s one the MTA doesn’t want to and cannot fund right now. Lander could.

It’s easy to talk about countdown clocks, but there’s been a concerted and logical effort to adopt a tracking system for a reasonable amount of money that doesn’t use clocks. Ideally, timers would be prevalent, but they are less reliable than GPS-based distance measurements. Now, though, a group of politicians want transit improvements at a concrete cost. Deliver the funding, and the clocks could become a reality.

December 12, 2012 71 comments
0 FacebookTwitterPinterestEmail
AsidesBusesStraphangers Campaign

NYC buses still pretty slow, sez Straphanger survey

by Benjamin Kabak December 11, 2012
written by Benjamin Kabak on December 11, 2012

Every year, the Straphangers Campaign goes through the pomp and circumstance of their Schleppie and Pokey Awards, and every year the outcome is the same. Some crosstown Manhattan bus is the slowest, and some north-south route is usually the least reliable. This year was no different as the M66 and M42 shared the Schleppie Award, and the M4 took home the Pokey.

The Straphangers’ report — full findings here — says that the two crosstown buses average around 3.9 miles per hour during their 12 noon runs. I’d imagine that time is even slower during rush hour when 42nd St. grows congested. “The M66 and M42 would lose a race to an amusement park bumper car,” Straphangers head Gene Russianoff said, “and be a lot less fun. A bumper car can go 4.3 miles per hour compared to the 3.9 miles of the Pokey Award winning buses.” The M4, meanwhile, suffered the most from problematic bus bunching and scheduling inaccuracies.

Of course, knowing that the buses are slow and unreliable is half the battle and barely news. While nodding at the city’s Select Bus Service as a clear sign of improvement, the Straphangers and Transportation Alternatives called for “investment,” but what kind of investment? The city should devote dedicated street space to buses, implement pre-board fare payment at most major routes and develop signal prioritization. Only then will buses begin to move faster than a healthy young adult can walk across town.

December 11, 2012 25 comments
1 FacebookTwitterPinterestEmail
Load More Posts

About The Author

Name: Benjamin Kabak
E-mail: Contact Me

Become a Patron!
Follow @2AvSagas

Upcoming Events
TBD

RSS? Yes, Please: SAS' RSS Feed
SAS In Your Inbox: Subscribe to SAS by E-mail

Instagram



Disclaimer: Subway Map © Metropolitan Transportation Authority. Used with permission. MTA is not associated with nor does it endorse this website or its content.

Categories

  • 14th Street Busway (1)
  • 7 Line Extension (118)
  • Abandoned Stations (31)
  • ARC Tunnel (52)
  • Arts for Transit (19)
  • Asides (1,244)
  • Bronx (13)
  • Brooklyn (126)
  • Brooklyn-Queens Connector (13)
  • Buses (291)
  • Capital Program 2010-2014 (27)
  • Capital Program 2015-2019 (56)
  • Capital Program 2020-2024 (3)
  • Congestion Fee (71)
  • East Side Access Project (37)
  • F Express Plan (22)
  • Fare Hikes (173)
  • Fulton Street (57)
  • Gateway Tunnel (29)
  • High-Speed Rail (9)
  • Hudson Yards (18)
  • Interborough Express (1)
  • International Subways (26)
  • L Train Shutdown (20)
  • LIRR (65)
  • Manhattan (73)
  • Metro-North (99)
  • MetroCard (124)
  • Moynihan Station (16)
  • MTA (98)
  • MTA Absurdity (233)
  • MTA Bridges and Tunnels (27)
  • MTA Construction (128)
  • MTA Economics (522)
    • Doomsday Budget (74)
    • Ravitch Commission (23)
  • MTA Politics (330)
  • MTA Technology (195)
  • New Jersey Transit (53)
  • New York City Transit (220)
  • OMNY (3)
  • PANYNJ (113)
  • Paratransit (10)
  • Penn Station (18)
  • Penn Station Access (10)
  • Podcast (30)
  • Public Transit Policy (164)
  • Queens (129)
  • Rider Report Cards (31)
  • Rolling Stock (40)
  • Second Avenue Subway (262)
  • Self Promotion (77)
  • Service Advisories (612)
  • Service Cuts (118)
  • Sponsored Post (1)
  • Staten Island (52)
  • Straphangers Campaign (40)
  • Subway Advertising (45)
  • Subway Cell Service (34)
  • Subway History (81)
  • Subway Maps (83)
  • Subway Movies (14)
  • Subway Romance (13)
  • Subway Security (104)
  • Superstorm Sandy (35)
  • Taxis (43)
  • Transit Labor (151)
    • ATU (4)
    • TWU (100)
    • UTU (8)
  • Triboro RX (4)
  • U.S. Transit Systems (53)
    • BART (1)
    • Capital Metro (1)
    • CTA (7)
    • MBTA (11)
    • SEPTA (5)
    • WMATA (28)
  • View from Underground (447)

Archives

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
  • Facebook
  • Twitter
  • Instagram

@2019 - All Right Reserved.


Back To Top