Campus Alert Archive
U-M

Worker stabbed at a construction site; suspect arrested after a five-hour manhunt

AI-generated · every claim is source-linked
MIstabbingemergency notificationhigh confidence
Compare →
Confirmed Threat

Around 6:20 PM EDT on September 18, 2025, a man was stabbed at the Kahn Health Care Pavilion construction site on the University of Michigan medical campus after the suspect was denied entry. U-M Emergency Alert sent two messages (initial at 6:20 PM EDT and a suspect-description follow-up at 7:11 PM EDT) and the suspect, Lagarien Thomas, 33, was arrested at 11:34 PM EDT after a five-hour Ann Arbor manhunt.

Alerts
7
Response
1 min
Killed
0
Injured
1
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

7 messages in sequence · 7 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 verbatim113 chars
UM EAlert Ann Arbor: 6:21pm Stabbing occurred Catherine/Zina Pitcher. Avoid Area. Updates: http://dpss.umich.edu
Verify this quote
@umichdpss on X (verbatim)x.comfind archived copies
Verbatim text of the UM EAlert sent at 6:21 PM EDT on September 18, 2025, pushed simultaneously via SMS, email, and X
DPSS uses minimalist 'EAlert' text (under 160 characters) so the SMS variant fits in a single message and includes a link for updates
The Catherine Street and Zina Pitcher Place intersection sits at the heart of the U-M Medical Campus next to the Kahn Pavilion construction site
Corrected to exact fxtwitter display text.
UPDATESMS+50 min
Verified verbatim104 chars
Update #1: 7:11 p.m. Stabbing suspect: Heavyset Black male in white shirt, tie, jeans. Call 911 if seen.
Verify this quote
U-M DPSS Emergency Alert 9/18/25 archivedpss.umich.edufind archived copies
Exact Update #1 text from official U-M DPSS emergency-alert archive (7:11 p.m. suspect description)
Suspect description came from witnesses at the Kahn Pavilion construction site after the assailant fled
UPDATESMS+1h 15m
Verified verbatim182 chars
Update #2: 7:36 p.m. Photo of suspect has been released. It may be found on DPSS X and Facebook accounts. Police asking for community to be alert and call 911 you see the individual.
Verify this quote
U-M DPSS Emergency Alert 9/18/25 — seq 3dpss.umich.edufind archived copies
Exact line from official DPSS emergency-alert archive
ALL CLEARSMS+5h 13m
Verified verbatim109 chars
Note: Suspect was arrested at 11:34 pm. There is no threat to the campus at this time. Investigation ongoing.
Verify this quote
U-M DPSS Emergency Alert 9/18/25 archivedpss.umich.edufind archived copies
Exact arrest/all-clear notice text from official U-M DPSS emergency-alert archive page
Lagarien Thomas, 33, arrested by Ann Arbor Police at approximately 11:34 PM EDT
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.

UM EAlert Ann Arbor: 6:21pm Stabbing occurred Catherine/Zina Pitcher. Avoid Area. Updates: http://dpss.umich.edu

  • Sourcepresent25/25

    Final assessment

    All reads agree the 'UM EAlert' branded signature identifies the sending system, so source is present.

    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: 'UM EAlert' branded signature.
    2. present: 'UM EAlert' branded signature.
    3. present: 'UM EAlert' branded signature.
    4. present: Branded "UM EAlert" signature.
    5. present: 'UM EAlert' branded signature.
    6. present: 'UM EAlert' branded signature.
    7. present: 'UM EAlert' branded signature.
    8. present: 'UM EAlert' identifies sender.
    9. present: 'UM EAlert' branded signature identifies the system.
    10. present: Labeled "UM EAlert"
    11. present: UM EAlert identifies the sender.
    12. present: UM EAlert branding identifies issuer.
    13. present: Branded 'UM EAlert' signature.
    14. present: Labeled 'UM EAlert' from Ann Arbor with dpss.umich.edu link.
    15. present: UM EAlert names the issuing system.
    16. present: Branded "UM EAlert" tied to dpss.umich.edu.
    17. present: 'UM EAlert' branded signature.
    18. present: 'UM EAlert' signature identifies sender.
    19. present: 'UM EAlert' branded signature.
    20. present: "UM EAlert" branded signature
    21. present: Branded 'UM EAlert' signature identifies the issuer.
    22. present: Labeled UM EAlert.
    23. present: 'UM EAlert' branded signature identifies the sender.
    24. present: Branded 'UM EAlert' signature.
    25. present: 'UM EAlert' branded signature.
  • Hazardpresent25/25

    Final assessment

    Unanimous agreement that 'Stabbing occurred' names a specific hazard.

    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. present: 'Stabbing occurred' names the hazard.
    2. present: 'Stabbing occurred' names the hazard specifically.
    3. present: 'Stabbing' named specifically.
    4. present: Names a stabbing specifically.
    5. present: 'Stabbing occurred' names the hazard.
    6. present: 'Stabbing occurred' names the hazard.
    7. present: 'Stabbing occurred' names the specific hazard.
    8. present: 'Stabbing' named.
    9. present: Names a stabbing.
    10. present: Names "Stabbing" as the hazard
    11. present: Names a stabbing as the specific hazard.
    12. present: Stabbing named explicitly.
    13. present: Names 'Stabbing occurred'.
    14. present: States 'Stabbing occurred'.
    15. present: Stabbing named as the hazard.
    16. present: Names "Stabbing."
    17. present: 'Stabbing occurred'.
    18. present: 'Stabbing' specifically named.
    19. present: Stabbing named.
    20. present: "Stabbing" specified
    21. present: Names 'Stabbing' as the specific hazard.
    22. present: Names a stabbing.
    23. present: 'Stabbing' names the hazard.
    24. present: States 'Stabbing occurred'.
    25. present: 'Stabbing occurred' names specific hazard.
  • Locationpresent25/25

    Final assessment

    All reads confirm the 'Catherine/Zina Pitcher' intersection is named as the specific location.

    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: 'Catherine/Zina Pitcher' named.
    2. present: 'Catherine/Zina Pitcher' location named.
    3. present: 'Catherine/Zina Pitcher'.
    4. present: Catherine/Zina Pitcher, Ann Arbor.
    5. present: 'Catherine/Zina Pitcher' intersection given.
    6. present: 'Catherine/Zina Pitcher'.
    7. present: 'Catherine/Zina Pitcher'.
    8. present: 'Catherine/Zina Pitcher.'
    9. present: Names Catherine/Zina Pitcher, Ann Arbor.
    10. present: Names Catherine/Zina Pitcher, Ann Arbor
    11. present: Names Catherine and Zina Pitcher location.
    12. present: Catherine/Zina Pitcher intersection, Ann Arbor.
    13. present: Names Catherine/Zina Pitcher, Ann Arbor.
    14. present: Names 'Catherine/Zina Pitcher'.
    15. present: Catherine/Zina Pitcher specified.
    16. present: Names "Catherine/Zina Pitcher."
    17. present: 'Catherine/Zina Pitcher' intersection, Ann Arbor.
    18. present: 'Catherine/Zina Pitcher' named.
    19. present: 'Catherine/Zina Pitcher'.
    20. present: "Catherine/Zina Pitcher" specified
    21. present: Names 'Catherine/Zina Pitcher' as the location.
    22. present: Catherine/Zina Pitcher intersection specified.
    23. present: 'Catherine/Zina Pitcher' location given.
    24. present: Names 'Catherine/Zina Pitcher'.
    25. present: 'Catherine/Zina Pitcher' given.
  • Guidancepresent25/25

    Final assessment

    Unanimous: 'Avoid Area' is a clear protective instruction.

    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: 'Avoid Area.'
    2. present: 'Avoid Area.'
    3. present: 'Avoid Area.'
    4. present: Instructs to avoid the area.
    5. present: 'Avoid Area.'
    6. present: 'Avoid Area.'
    7. present: 'Avoid Area.'
    8. present: 'Avoid Area.'
    9. present: Instructs to avoid area.
    10. present: Instructs to avoid area
    11. present: Instructs to avoid area.
    12. present: Avoid Area instructed.
    13. present: Instructs to 'Avoid Area'.
    14. present: Instructs 'Avoid Area.'
    15. present: Instructs to avoid area.
    16. present: Instructs to "Avoid Area."
    17. present: 'Avoid Area.'
    18. present: 'Avoid Area.'
    19. present: 'Avoid Area.'
    20. present: "Avoid Area"
    21. present: Instructs recipients to 'Avoid Area.'
    22. present: Instructs to avoid area.
    23. present: 'Avoid Area.'
    24. present: Instructs to 'Avoid Area'.
    25. present: 'Avoid Area.'
  • Timepresent25/25

    Final assessment

    All reads agree '6:21pm' provides a specific clock 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: '6:21pm'.
    2. present: '6:21pm' given.
    3. present: '6:21pm' given.
    4. present: Gives 6:21pm as the time.
    5. present: '6:21pm' given.
    6. present: '6:21pm' given.
    7. present: '6:21pm'.
    8. present: '6:21pm' given.
    9. present: Gives '6:21pm'.
    10. present: States "6:21pm"
    11. present: Gives clock time, 6:21pm.
    12. present: 6:21pm given.
    13. present: Specifies '6:21pm'.
    14. present: Gives '6:21pm'.
    15. present: 6:21pm given.
    16. present: Gives a clock time, "6:21pm."
    17. present: '6:21pm' given.
    18. present: '6:21pm' given.
    19. present: '6:21pm' given.
    20. present: "6:21pm" given
    21. present: States '6:21pm' as the time.
    22. present: 6:21pm specified.
    23. present: '6:21pm' clock time given.
    24. present: States '6:21pm'.
    25. present: '6:21pm' given.
  • Impactabsent0/25

    Final assessment

    Unanimous: the alert states only the hazard name with no consequence or severity described.

    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 or severity beyond the hazard name.
    2. absent: No stated consequence beyond the hazard name.
    3. absent: No stated consequence or severity beyond naming the hazard.
    4. absent: No stated consequence or severity.
    5. absent: No stated consequence or severity beyond naming the stabbing.
    6. absent: No stated consequence beyond naming the stabbing.
    7. absent: No stated consequence or severity beyond the event.
    8. absent: No stated consequence beyond hazard name.
    9. absent: No stated consequence or severity beyond the hazard name.
    10. absent: No stated consequence beyond hazard name
    11. absent: No stated consequence or severity.
    12. absent: No stated consequence beyond hazard name.
    13. absent: No stated consequence or severity beyond the hazard name.
    14. absent: No stated consequence or severity.
    15. absent: No stated consequence or severity beyond hazard name.
    16. absent: No stated consequence or severity beyond naming the stabbing.
    17. absent: No stated consequence or severity beyond naming the stabbing.
    18. absent: No stated consequence or severity beyond the hazard name.
    19. absent: No stated consequence beyond the hazard name.
    20. absent: No stated consequence beyond hazard name
    21. absent: No stated consequence beyond naming the hazard.
    22. absent: No stated consequence described.
    23. absent: No stated consequence or severity beyond the hazard name.
    24. absent: No stated consequence or severity.
    25. absent: No stated consequence beyond hazard name.

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

About this analysis
Context

Background

On the evening of Thursday, September 18, 2025, a man attempted to enter the D. Dan and Betty Kahn Health Care Pavilion construction site on U-M's medical campus near the intersection of Catherine Street and Zina Pitcher Place. After being denied entry, Lagarien Thomas, 33, allegedly stabbed a construction worker and fled. U-M's Division of Public Safety and Security issued an emergency alert at approximately 6:20 PM EDT, followed by a suspect-description update at 7:11 PM EDT after witnesses provided more detail. Ann Arbor Police led a five-hour manhunt and arrested Thomas at 11:34 PM EDT. The victim survived with non-life-threatening injuries. The incident drew renewed attention to construction-site security on the medical campus and to U-M's use of layered alert updates rather than single mass notifications during evolving threats.
Analysis

Key Findings

U-M's three-message alert pattern (initial, suspect description, all-clear) is consistent with DPSS emergency-notification protocol for active suspects
The 51-minute gap between the initial alert and the suspect-description update reflects the time required to obtain a usable description from witnesses
The case shows the value of geographically specific alerts: the initial message named the exact intersection rather than a generic 'medical campus' designation
U-M Emergency Alert remained active for roughly 5 hours and 14 minutes from initial alert to all-clear
Outcome
Lagarien Thomas, 33, was arrested by Ann Arbor Police at approximately 11:34 PM EDT on September 18, 2025. The victim, a construction worker, was transported with non-life-threatening injuries.
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
    MEDIA RELEASE: Stabbing Near Catherine Street and Zina Pitcher Place (DPSS)
    dpss.umich.edu
    archived copy
  2. Official
    U-M Emergency Alert 9/18/25 (DPSS)
    dpss.umich.edu
    archived copy
  3. News
    Suspect in custody after one person stabbed on University of Michigan campus (CBS Detroit)
    cbsnews.com
    archived copy
  4. News
    University of Michigan Stabbing Incident: Suspect Apprehended Following Manhunt (Campus Safety Magazine)
    campussafetymagazine.com
    archived copy
  5. News
    University of Michigan stabbing suspect arrested (FOX 2 Detroit)
    fox2detroit.com
    archived copy
  6. Official
    @umichdpss on X
    x.com
    archived copy
Cite this case

Campus Alert Archive. "University of Michigan: Worker stabbed at a construction site; suspect arrested after a five-hour manhunt." Incident of September 18, 2025. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/university-of-michigan-construction-site-stabbing-2025-09-18/

Download case JSON

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

Tags
stabbingmichiganpublic-r1medical-campusmanhuntconstruction-siteu-m-emergency-alert
Added May 2026Updated July 2026Via ingestion