Arbor Oaks — HUD inspection scores

Public housing · 5610 Mcclean Blvd, Baltimore, MD 21214

Latest published score NSPIRE

59 Failing

out of 100 Inspected April 21, 2025

06080100

Scores higher than 4% of Maryland’s 816 currently scored properties · state median 91

Under NSPIRE, a score below 60 is failing; 60–79 puts a property on a more frequent inspection cycle.

Every published inspection

Scores as published by HUD. NSPIRE (2023–) and REAC (2000–2023) scores come from different standards and are not directly comparable.
Inspection date	Score	Standard
April 21, 2025	59	NSPIRE
January 29, 2020	68	REAC (UPCS)
February 4, 2019	50	REAC (UPCS)
July 17, 2017	52	REAC (UPCS)
July 24, 2015	92	REAC (UPCS)
September 8, 2014	69	REAC (UPCS)
February 18, 2009	86.14	REAC (UPCS)
November 8, 2007	76.37	REAC (UPCS)
January 24, 2006	79.94	REAC (UPCS)
September 29, 2004	86.68	REAC (UPCS)
January 9, 2003	86.83	REAC (UPCS)
November 6, 2001	97.73	REAC (UPCS)
September 28, 2000	69.56	REAC (UPCS)

HUD's published files sample the record: each snapshot carries a property's latest score at publication, so an inspection can be missing between snapshots, and no inspections conducted 2010–2012 appear in any file HUD still publishes. History here is assembled from every file HUD offers.

Property record

Program: Public housing
HUD development id: MD002000101
Managed by: Housing Authority Of Baltimore City (PHA MD002)
Inspections on file: 13 since 2000

Browse the record

Inspection cadence

An inspection date a year or three back is normal: HUD inspects on a risk-based cycle, less often the better the last score, and this site reflects HUD's newest published file, refreshed weekly. How often HUD inspects

Where this came from

Scores come from HUD USER's physical inspection scores datasets (public housing and multifamily, 2000 to present). The numbers are HUD's, not ours. A score below 60 obligates HUD to act, but a low score alone does not prove current conditions — inspections can be years apart.