Skip to content
Campus Alert Archive
U-M

Self-harm standoff in a research complex parking lot; all-clear in about two hours

AI-generated · every claim is source-linked
MIpolice activityemergency notificationhigh confidence
Confirmed Threat

On the evening of December 18, 2024, the University of Michigan Division of Public Safety and Security issued a U-M Emergency Alert at 9:24 p.m. EST warning the campus community to avoid Building 520 of the North Campus Research Complex. The alert was later expanded to a wider 2800 Plymouth Road perimeter as an individual threatening self-harm remained barricaded in a parking lot between the NCRC and the University of Michigan Transportation Research Institute (UMTRI). Officers contained the situation and issued the all-clear at 11:37 p.m. EST.

Alerts
5
Response
0 min
Killed
0
Injured
0
Institution
University of Michigan
Public R1 · MI
All U-M cases →
~52,000 studentsRaveU-M Emergency Alert
Official alert policy
Read when and how U-M says it will use U-M Emergency Alert: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

5 messages in sequence · 5 verified verbatim

Confirmed wording is transcribed character-for-character from a primary source. Use Verify this quote under each message to open that source in a new tab and compare the text yourself.

INITIAL ALERTTwitter/X
Verified verbatim160 chars
Ann Arbor: 2124 Emergency NCRB520. Avoid the area. Officers on scene. Do not enter the area until cleared. Updates: http://dpss.umich.edu https://dpss.umich.edu
Official campus X cascade recovered in PR6.
UPDATETwitter/X+19 min
Verified verbatim131 chars
Ann Arbor: 2144 UPDATE LOCATION NCRC#520. 2800 PLYMOUTH RD. OFFICERS IN AREA. PLEASE AVOID THE AREA. Updates: http://dpss.umich.edu
Verbatim text confirmed from the U-M DPSS official archive at news.dpss.umich.edu/2024/12/4797
Alert includes the time stamp '9:24 p.m.' embedded in the message body, a U-M DPSS formatting convention
Names NCRC Building 520 specifically rather than the whole complex, narrowing the avoidance perimeter
Corrected to exact fxtwitter display text.
UPDATESMS+1h 1m
Verified verbatim227 chars
UPDATE #2: 10:26 p.m. Situation is ongoing at the parking lot between North Campus Research Complex (NCRC) and UMTRI (University of MI Transportation Research Institute). East side of Huron Parkway. Avoid all surrounding areas.
Exact UPDATE #2 line from official DPSS 12/18/24 chronology
Message elements

How the first alert is built

To check this alert, Claude (an AI) read it in full 25 separate times, independently. Each read decided whether the message answers each of the six questions and gave a short reason. A final reviewer then weighed all 25 and wrote the plain-English verdict you see when you open a row. The score (for example 22/25) is how many reads agreed; the 25 individual reads are tucked underneath if you want to check them.

Ann Arbor: 2124 Emergency NCRB520. Avoid the area. Officers on scene. Do not enter the area until cleared. Updates: http://dpss.umich.edu https://dpss.umich.edu

  • Sourceabsent8/25

    Final assessment

    Reads split, but the majority find no named agency in the text itself, only a cryptic code ('NCRB520') and a link to dpss.umich.edu that implies but doesn't state the Division of Public Safety and Security as sender.

    Who is sending the alert and who is responding. People act faster on a message from a clearly identifiable, credible sender, such as a named department, the police, or a branded alert system, than on an anonymous notice. A branded signature counts.

    See all 25 individual reads
    1. present: Links to 'dpss.umich.edu', the university's public safety department.
    2. absent: '2124 Emergency NCRB520' is a code, no clear issuing agency named though implicitly DPSS via link
    3. absent: No named agency or branded signature beyond generic 'Ann Arbor:' timestamp prefix.
    4. absent: No specific agency named, only implied via dpss.umich.edu link, 'Officers on scene' is generic.
    5. present: dpss.umich.edu link identifies the Division of Public Safety and Security as source.
    6. present: Points to 'dpss.umich.edu', the campus police site.
    7. absent: No specific agency identified beyond location label 'Ann Arbor:'.
    8. present: Links to 'dpss.umich.edu' identifying the Division of Public Safety and Security as sender.
    9. absent: No department name or branded alert signature, only 'Ann Arbor' location label.
    10. absent: 'Ann Arbor' with dpss.umich.edu link implies DPSS but not clearly named as sender in text.
    11. present: Links to dpss.umich.edu, identifying DPSS as source.
    12. absent: No specific sending agency named, only a generic 'Emergency' code label and link.
    13. absent: No sender, agency, or branded signature identifies who issued this.
    14. present: Links to 'dpss.umich.edu', the university's public safety department.
    15. absent: No sender, department, or branded system identified anywhere in the text (only a link to dpss.umich.edu).
    16. absent: Only references 'dpss.umich.edu' link, no clear sender/agency name in body text.
    17. absent: Only 'Officers on scene' given, no named agency or branded alert signature.
    18. present: Refers to dpss.umich.edu, the Division of Public Safety and Security, and 'Officers on scene'.
    19. absent: No sender or agency named beyond a link to dpss.umich.edu, not stated as sender in text itself.
    20. absent: No named issuing authority in the text; only a location/case code and website link.
    21. present: References 'dpss.umich.edu', Division of Public Safety and Security officers.
    22. absent: Only cryptic 'Emergency NCRB520' with a dpss.umich.edu link, no named agency or clear sender identified
    23. absent: No sender or issuing agency identified beyond a code label 'NCRB520'.
    24. absent: No specific agency named in the text itself, only a code and a link to dpss.umich.edu.
    25. absent: No sending agency or institution name given, only 'Ann Arbor' dateline and generic 'Officers on scene'.
  • Hazardabsent0/25

    Final assessment

    Unanimous: 'Emergency NCRB520' is only a code, no specific hazard type is named.

    What the threat actually is. A complete warning names the specific danger, such as a shooter, a fire, a tornado, or a gas leak, rather than a vague emergency, because people decide what to do based on what they are facing.

    See all 25 individual reads
    1. absent: 'Emergency NCRB520' is a code, no specific threat type named.
    2. absent: no specific hazard type named, just 'Emergency NCRB520' code
    3. absent: Only says 'Emergency NCRB520', no specific threat type named.
    4. absent: 'Emergency NCRB520' is a generic code without naming a specific threat.
    5. absent: 'Emergency NCRB520' is a coded label, not a named specific threat.
    6. absent: 'Emergency NCRB520' is a code, not a named threat.
    7. absent: 'Emergency NCRB520' is a code, not a named hazard type.
    8. absent: Only 'Emergency NCRB520' is a code, no plain-language hazard named.
    9. absent: Only labeled 'Emergency NCRB520' without naming a specific threat type.
    10. absent: 'Emergency NCRB520' is a code, no specific hazard type named.
    11. absent: Only 'Emergency NCRB520' given, a code with no specific threat named.
    12. absent: 'Emergency NCRB520' is a code, not a named specific hazard.
    13. absent: 'Emergency NCRB520' is a code, not a named threat type.
    14. absent: 'Emergency NCRB520' is a code, not a named specific threat.
    15. absent: Only 'Emergency NCRB520' code given, no specific threat named.
    16. absent: 'Emergency NCRB520' is a code, not a named specific hazard.
    17. absent: 'Emergency NCRB520' is a code, not a named specific threat.
    18. absent: Only 'Emergency NCRB520' given as a code, no specific hazard type named.
    19. absent: Only 'Emergency NCRB520' code given, no specific hazard named.
    20. absent: 'Emergency NCRB520' is a generic code, no specific hazard type named.
    21. absent: 'Emergency NCRB520' is a code without naming a specific hazard.
    22. absent: 'Emergency NCRB520' is a code, not a named specific hazard
    23. absent: Only a code 'Emergency NCRB520' is given with no specific hazard type.
    24. absent: 'Emergency NCRB520' is a code, not a named specific threat.
    25. absent: Only 'Emergency NCRB520' code with no plain-language hazard description.
  • Locationpresent16/25

    Final assessment

    Majority read the 'NCRB520' code plus 'the area' as at least a location reference, though a substantial minority found it too cryptic to count as a named place.

    Where the threat is. Saying whether danger is in a specific building, a part of campus, or area-wide lets people judge their own proximity and choose a safe direction. Without a where, a warning is hard to act on precisely.

    See all 25 individual reads
    1. present: 'NCRB520' functions as a location designator referenced as 'the area'.
    2. present: 'NCRB520' names a location code/area
    3. present: Names NCRB (implied building) via code, treated as location reference.
    4. present: 'NCRB520' area referenced as a location code.
    5. present: Names the NCRB520 area.
    6. present: Refers to 'the area' officers are clearing, though unnamed specifically.
    7. absent: 'NCRB520' is a code reference, no clear geographic location named.
    8. present: Names 'NCRB520' area.
    9. absent: No specific location beyond a code label 'NCRB520', not a named place.
    10. absent: No specific location named beyond 'the area', generic.
    11. absent: 'NCRB520' is a cryptic code, not a clearly named place.
    12. absent: No specific building or street named, only 'the area.'
    13. present: 'NCRB520' names a location code and 'Ann Arbor.'
    14. absent: Only refers to 'the area' without naming a specific place.
    15. present: Implies area near NCRB via code reference, but vague; still counted as an area reference.
    16. present: References area 'NCRB520' as a place code.
    17. present: 'Ann Arbor' and area implied via 'NCRB' though vague.
    18. absent: No specific location beyond a code reference 'NCRB520', not an identifiable place name for a reader.
    19. present: Implies 'NCRB' location via the code, referencing a specific building code.
    20. present: 'Ann Arbor' and implied area near NCRB give location context.
    21. present: Names 'NCRB520' area.
    22. present: Names 'NCRB520' as area/location reference
    23. absent: No specific place named beyond an unexplained code.
    24. present: References 'NCRB520' as a location code and 'the area'.
    25. absent: No specific area or building beyond a code reference 'NCRB520'.
  • Guidancepresent25/25

    Final assessment

    Unanimous: 'Avoid the area...Do not enter the area until cleared' gives explicit protective instructions.

    The protective action to take. A clear, specific instruction, such as shelter in place, evacuate, avoid the area, or run-hide-fight, drives faster and more correct protective behavior than describing the threat alone.

    See all 25 individual reads
    1. present: Instructs 'Do not enter the area until cleared'.
    2. present: 'Avoid the area...Do not enter the area until cleared'
    3. present: Instructs 'Avoid the area...Do not enter the area until cleared.'
    4. present: 'Avoid the area...Do not enter the area until cleared' explicit instructions.
    5. present: Instructs to 'Avoid the area' and 'Do not enter the area until cleared'.
    6. present: Instructs 'Do not enter the area until cleared'.
    7. present: 'Avoid the area...Do not enter the area until cleared.'
    8. present: Instructs 'Avoid the area...Do not enter the area until cleared.'
    9. present: Instructs 'Avoid the area... Do not enter the area until cleared.'
    10. present: 'Avoid the area...Do not enter the area until cleared.'
    11. present: Instructs 'Avoid the area... Do not enter the area until cleared.'
    12. present: Instructs 'Avoid the area... Do not enter the area until cleared.'
    13. present: 'Avoid the area...Do not enter the area until cleared.'
    14. present: Instructs to 'Avoid the area' and 'Do not enter the area until cleared'.
    15. present: Instructs 'Avoid the area... Do not enter the area until cleared.'
    16. present: Instructs 'Avoid the area...Do not enter the area until cleared'.
    17. present: 'Avoid the area. Do not enter the area until cleared.'
    18. present: Instructs 'Avoid the area' and 'Do not enter the area until cleared'.
    19. present: Instructs 'Avoid the area...Do not enter the area until cleared.'
    20. present: 'Avoid the area...Do not enter the area until cleared' gives explicit protective action.
    21. present: Instructs 'Avoid the area...Do not enter the area until cleared'.
    22. present: Instructs 'Avoid the area...Do not enter the area until cleared'
    23. present: Instructs 'Avoid the area... Do not enter the area until cleared.'
    24. present: Instructs 'Avoid the area...Do not enter the area until cleared.'
    25. present: Instructs 'Avoid the area' and 'Do not enter the area until cleared'.
  • Timepresent15/25

    Final assessment

    Majority read '2124' as a military-format clock time (9:24 PM), though a meaningful minority found it too ambiguous, reading it as part of the case code rather than a time.

    When the message applies. A timestamp, the word now or immediately, or a phrase like until further notice tells the reader whether the danger is current and how quickly to act.

    See all 25 individual reads
    1. present: Gives '2124', likely a 24-hour clock time.
    2. absent: no clock time or date given
    3. present: Gives '2124' as a time marker.
    4. present: '2124' given as a time code.
    5. present: States '2124', a military clock time.
    6. present: Gives '2124' (9:24 PM).
    7. absent: No clock time or date given, '2124' appears to be a code not a time.
    8. present: Gives '2124' as a time code.
    9. present: States '2124', a time code.
    10. absent: No clock time given beyond '2124' which appears to be a code, not clearly a time.
    11. absent: No time given.
    12. present: Gives '2124' as a time marker.
    13. absent: No clock time or date given.
    14. present: Gives '2124', a military-time timestamp.
    15. absent: No clock time or date given.
    16. present: States '2124', a time code.
    17. present: '2124' given as a time code.
    18. present: Gives '2124' as a timestamp.
    19. present: Gives '2124' as a time reference (9:24 PM in police time notation).
    20. present: '2124' likely denotes 9:24 PM military time.
    21. absent: No time reference given.
    22. absent: No specific time given
    23. absent: No clock time or date given, only a numeric code '2124'.
    24. absent: No clock time or date given, only '2124' which is ambiguous.
    25. present: Gives '2124' as a time reference.
  • Impactabsent0/25

    Final assessment

    Unanimous: no stated consequence or severity is conveyed.

    What the hazard could do to the people in its path. Beyond naming the threat, a complete warning conveys its potential consequences or severity, such as that a tornado can level buildings or that a leak could be explosive, so recipients grasp how much danger they are in. Research on warning message content finds that a concrete impact statement helps people personalize their risk and act sooner.

    See all 25 individual reads
    1. absent: No stated consequence.
    2. absent: no stated consequence or severity
    3. absent: No stated consequence or severity.
    4. absent: No stated potential harm or severity.
    5. absent: No stated potential harm.
    6. absent: No stated harm or severity.
    7. absent: No stated potential harm or severity conveyed.
    8. absent: No explicit statement of potential harm.
    9. absent: No stated potential harm or severity.
    10. absent: No stated potential harm/severity.
    11. absent: No stated consequence or severity.
    12. absent: No explicit statement of potential harm or severity.
    13. absent: No stated harm or severity.
    14. absent: No explicit statement of potential harm.
    15. absent: No explicit statement of harm or severity.
    16. absent: No stated consequence or severity.
    17. absent: No stated consequence or severity given.
    18. absent: No explicit statement of potential harm or severity.
    19. absent: No explicit statement of potential harm or severity.
    20. absent: No stated consequence or severity conveyed.
    21. absent: No stated consequence.
    22. absent: No statement of potential harm or severity
    23. absent: No stated potential harm or severity.
    24. absent: No explicit statement of potential harm.
    25. absent: No stated potential harm.

Systematic AI judgments with visible reasoning, not human-validated codings.

About this analysis
Context

Background

The University of Michigan's December 18, 2024 emergency alert was issued by the Division of Public Safety and Security (DPSS) at 9:24 p.m. EST and asked the campus to avoid Building 520 of the North Campus Research Complex, the sprawling former Pfizer pharmaceutical campus on Plymouth Road that U-M acquired in 2009. About 20 minutes after the initial alert, DPSS expanded the avoidance perimeter from a single building to the broader 2800 Plymouth Road address. Around 10:26 p.m. EST, officials confirmed the situation was unfolding in the parking lot between the NCRC and the University of Michigan Transportation Research Institute (UMTRI), on the east side of Huron Parkway. At 11:14 p.m. EST, U-M characterized the situation publicly for the first time as involving an individual threatening self-harm, a choice that communicated there was no third-party threat without naming the individual. The all-clear was issued at 11:37 p.m. EST, about two hours and 13 minutes after the initial alert. The DPSS permalink page preserves the alert under the title 'U-M Emergency Alert 12/18/24: Self-harm Threat [All Clear].' The incident drew attention because mental-health emergencies have not historically triggered the same campus-wide emergency notifications that violent threats do, and U-M's choice to push a Rave alert for a contained self-harm standoff illustrates the evolving role of mass notification in non-attacker scenarios.
Analysis

Key Findings

U-M used its campus-wide emergency alert system for a contained self-harm standoff, a documented example of mass notification in a non-attacker scenario
The alert scope was expanded (one building to a wider perimeter) as the situation moved from inside Building 520 to an outdoor parking lot, demonstrating dynamic perimeter adjustment
By publicly labeling the incident as a 'self-harm threat', DPSS communicated that there was no third-party threat while withholding identifying details
Outcome
The standoff involved a single individual threatening self-harm in a vehicle in the parking lot east of Huron Parkway. No one else was harmed. The all-clear came at approximately 11:37 p.m. EST, about two hours and 13 minutes after the initial alert. U-M DPSS did not publicly release further details about the individual, citing privacy considerations consistent with HIPAA and self-harm reporting norms.
Provenance

Sources

Every claim on this page is meant to be checkable. Open the links below (and the Verify this quote control under each confirmed alert) to read the original university, news, or archive page yourself. Hostnames are shown so you can see where you are going; archived copies survive when live pages move or disappear. See also our methodology.

  1. Official
  2. Social
  3. News
  4. News
  5. News
  6. Official
  7. Official
Cite this case

Campus Alert Archive. "University of Michigan: Self-harm standoff in a research complex parking lot; all-clear in about two hours." Incident of December 18, 2024. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/university-of-michigan-ncrc-self-harm-threat-2024-12-18/

Download case JSON

Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.

Tags
police-activityself-harmbig-tenmichiganncrchuron-parkwaydpssmental-health-response
Added May 2026Updated July 2026Via ingestion