Stalled Development in the 39th Council District

We need to make these sites into assets for the community. Many of these developments are causing real hazards for their neighbors, with fences falling down on sidewalks, loose construction debris that can become deadly in high winds, and unsecured sites that are dangerous for children and an invitation to squatting.

Help the effort to convert local blight to community benefit by providing feedback and tracking the progress of each site.
Leave comments below on a individual site to update us on the conditions. If you call 311 about an issue, please leave a complaint number in the comment.

Tuesday, June 1, 2010

174 Garfield Place, Park Slope

(between 6th and 7th Avenues)



Project type: Existing building

Project description: None (vacant building)

Status: UPDATE 8/2010: Site sold to new developer who plans on building at the site. See Brooklyn Paper article here.

UPDATE: DOB adds to "Stalled Sites" list for extra monitoring: 2/16/2010

Background: In 2006 and 2007, partial demolition work was undertaken without a permit. The work ceased, and the building was sealed. The building has 15 unresolved violations, the most recent of which indicated that the brickwork and cornice are defective and loose. There have been complaints about the building being open and accessible, but the DOB has determined that it is sufficiently closed. Windows and doors are cemented, but the front yard is open and accessible, in poor shape and has debris. Permits have expired.

2 comments:

  1. This afternoon, March 13, loose wood trim on the fourth floor of the facade fell near sidewalk. Shed that had been erected to catch debris failed to catch it, as it failed to catch large portion of stone that fell in 2006.
    311 was called (compl. # 3335367).
    Shed itself appears to be loosely held together by nails on the side.

    ReplyDelete
  2. On March 12 (Friday) plywood was nailed over door. This provides a welcome but TEMPORARY solution to safety issues block association has been pointing out during past year. Does anyone know who did it and whether a more permanent solution might be on the way?

    ReplyDelete