Campus Alert Archive
OSU

Stabbing, April 10, 2026

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

On the evening of April 10, 2026, a 19-year-old man was fatally stabbed at the Lincoln Tower turf fields on Ohio State's campus. OSU did not issue a Buckeye Alert because a 15-year-old suspect was in custody within minutes. The university only notified the public via brief Twitter/X posts at 8:47 PM EDT, prompting student criticism of OSU's notification choices.

Alerts
2
Response
62 min
Killed
1
Injured
0
Institution
The Ohio State University
Public R1 · OH
All OSU cases →
~60,000 studentsBuckeye Alert
Official alert policy
Read when and how OSU says it will use Buckeye Alert: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

2 messages in sequence · 2 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 verbatim253 chars
At approx. 7:45 pm, there was an altercation between two groups on the Lincoln Tower turf fields. One person, not affiliated with OSU, was stabbed. Police responded and quickly detained the suspect. There is no ongoing threat. Victim transported to WMC.
Verify this quote
@OSU_EMFP on X (verbatim Lincoln Tower stabbing initial notice)x.comfind archived copies
Full text from official @OSU_EMFP X status; no Buckeye Alert was issued because the suspect was detained and there was no ongoing threat
Near-duplicate also posted by @OSUPOLICE five minutes later (status/2042767662443307101) with minor comma difference after 'person'
FOLLOW-UPTwitter/X+17h 49m
Verified verbatim280 chars
The victim in Friday night’s stabbing is deceased. Our thoughts are with his family. The suspect is in custody & the investigation continues. The victim & suspect are not affiliated with the university & there is no ongoing threat.Anyone with info should call OSUPD @ 614-292-2121
Verify this quote
@OSU_EMFP on X (verbatim raw t.co)x.comfind archived copies
Full text from official @OSU_EMFP X status announcing the victim's death; same wording simultaneously posted by @OSUPOLICE
Note no space before 'Anyone' after the period — preserved exactly as posted
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.

At approx. 7:45 pm, there was an altercation between two groups on the Lincoln Tower turf fields. One person, not affiliated with OSU, was stabbed. Police responded and quickly detained the suspect. There is no ongoing threat. Victim transported to WMC.

  • Sourceabsent4/25

    Final assessment

    Most reads find no named sender, agency, or branded alert system, only a generic 'Police responded'; a minority treated that phrase or an OSU reference as sufficient identification, but the majority holds no clear issuing authority is stated.

    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. absent: No sender or authority named, only references 'Police responded'.
    2. absent: No branded alert system or named agency identifies itself, only generic "Police responded".
    3. absent: No sender, agency, or branded alert signature identified in the text.
    4. absent: No sender, agency, or branded signature identified, only 'Police responded'.
    5. absent: No sender identified; mentions 'Police responded' but no issuing authority named.
    6. present: "Police responded" identifies responding agency.
    7. present: References 'Police responded' as the responding authority.
    8. absent: No sender, agency, or branded system identified in the text.
    9. absent: No issuing authority or branded signature named, only "Police responded".
    10. present: References 'OSU' and states 'Police responded', naming institution and agency.
    11. absent: No sender or authority named; only "Police responded" mentioned generically.
    12. present: Mentions police responded, implying police as issuing authority; also references OSU context.
    13. absent: No sender, agency, or branded signature identified in the text.
    14. absent: No sender identity, branding, or issuing agency stated; "Police responded" is generic.
    15. absent: No sender or issuing authority named.
    16. absent: No sender/authority named, only references 'OSU' and 'WMC'
    17. absent: No sender or issuing authority identified in the text.
    18. absent: No sender or authority named, just 'Police responded'.
    19. absent: No sender, agency, or branded alert name identified in the text.
    20. absent: No sender or authority explicitly identified in the text.
    21. absent: No sender or issuing authority identified in the text.
    22. absent: No sender or authority named.
    23. absent: No sender or authority named in the text.
    24. absent: No sender or authority explicitly named, though police mentioned as responders.
    25. absent: No sender, agency, or branded system identified; only "Police responded".
  • Hazardpresent25/25

    Final assessment

    Unanimous that 'One person...was stabbed' names the 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: Names 'stabbed' and an 'altercation'.
    2. present: Names the hazard as a stabbing: "One person... was stabbed".
    3. present: Names 'stabbed' specifically.
    4. present: Names 'one person...was stabbed'.
    5. present: States 'One person ... was stabbed'.
    6. present: Stabbing named.
    7. present: Names a person 'stabbed' as the hazard.
    8. present: States 'One person...was stabbed'.
    9. present: "was stabbed" names the threat.
    10. present: States 'One person... was stabbed'.
    11. present: States "was stabbed".
    12. present: Stabbing during an altercation named.
    13. present: States one person was stabbed.
    14. present: "One person...was stabbed" names the hazard.
    15. present: 'One person... was stabbed'.
    16. present: 'One person...was stabbed'
    17. present: Names person 'was stabbed'.
    18. present: States 'stabbed'.
    19. present: States 'One person... was stabbed'.
    20. present: Names person 'was stabbed'.
    21. present: States 'One person... was stabbed'.
    22. present: 'stabbed'.
    23. present: States 'One person... was stabbed'.
    24. present: A stabbing.
    25. present: States "was stabbed".
  • Locationpresent25/25

    Final assessment

    Unanimous: the 'Lincoln Tower turf fields' is a specific named 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: States 'Lincoln Tower turf fields'.
    2. present: Gives "the Lincoln Tower turf fields".
    3. present: Gives 'Lincoln Tower turf fields'.
    4. present: Lincoln Tower turf fields.
    5. present: Names 'Lincoln Tower turf fields'.
    6. present: Lincoln Tower turf fields.
    7. present: Names 'the Lincoln Tower turf fields'.
    8. present: Gives 'Lincoln Tower turf fields'.
    9. present: "Lincoln Tower turf fields".
    10. present: States 'the Lincoln Tower turf fields'.
    11. present: Names "Lincoln Tower turf fields".
    12. present: Lincoln Tower turf fields.
    13. present: Names Lincoln Tower turf fields.
    14. present: "Lincoln Tower turf fields".
    15. present: 'Lincoln Tower turf fields'.
    16. present: 'Lincoln Tower turf fields'
    17. present: Names 'Lincoln Tower turf fields'.
    18. present: Names 'Lincoln Tower turf fields'.
    19. present: Names 'Lincoln Tower turf fields'.
    20. present: Lincoln Tower turf fields given.
    21. present: Gives 'Lincoln Tower turf fields'.
    22. present: 'Lincoln Tower turf fields'.
    23. present: Names 'Lincoln Tower turf fields'.
    24. present: Lincoln Tower turf fields.
    25. present: Names "Lincoln Tower turf fields".
  • Guidanceabsent0/25

    Final assessment

    Unanimous: the message reports police detained the suspect and states there is no ongoing threat, but gives no protective action instruction to recipients.

    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. absent: No protective action instruction to recipients.
    2. absent: No protective action instruction is given, and it states "There is no ongoing threat."
    3. absent: No protective action instructed to recipients.
    4. absent: No protective action instructed to recipients.
    5. absent: No protective instruction given, just states there is no ongoing threat.
    6. absent: No protective action instructed to recipients, only states outcome.
    7. absent: No protective action instructed; states there is no ongoing threat.
    8. absent: States police 'quickly detained the suspect', no instruction to recipients.
    9. absent: No protective action instructed to recipients.
    10. absent: No instruction to the recipient, states 'There is no ongoing threat'.
    11. absent: No instruction to recipients, states there is "no ongoing threat".
    12. absent: No protective action instructed to recipients.
    13. absent: No instruction to recipients, only states police responded and detained suspect.
    14. absent: No instruction to recipients, states threat resolved.
    15. absent: No instruction given, states 'no ongoing threat'.
    16. absent: No instruction given, just states 'no ongoing threat'
    17. absent: No protective action instructed to recipients.
    18. absent: No instruction to recipients, states threat is over.
    19. absent: No protective action instructed; states 'no ongoing threat'.
    20. absent: No instruction to recipients, only describes police response.
    21. absent: No protective instruction given, only states police response and 'no ongoing threat'.
    22. absent: No instruction to recipients.
    23. absent: No protective action instructed to recipients.
    24. absent: States no ongoing threat, no protective instruction given.
    25. absent: No instruction to recipients; states no ongoing threat.
  • Timepresent25/25

    Final assessment

    Unanimous: 'At approx. 7:45 pm' gives 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: Gives 'approx. 7:45 pm'.
    2. present: States "At approx. 7:45 pm".
    3. present: States 'At approx. 7:45 pm'.
    4. present: Gives 'approx. 7:45 pm'.
    5. present: Gives 'approx. 7:45 pm'.
    6. present: "At approx. 7:45 pm" given.
    7. present: States 'At approx. 7:45 pm'.
    8. present: States 'At approx. 7:45 pm'.
    9. present: "At approx. 7:45 pm".
    10. present: States 'At approx. 7:45 pm'.
    11. present: Gives "approx. 7:45 pm".
    12. present: At approx. 7:45 pm.
    13. present: Gives approx. 7:45 pm.
    14. present: "At approx. 7:45 pm".
    15. present: 'At approx. 7:45 pm'.
    16. present: 'At approx. 7:45 pm'
    17. present: States 'At approx. 7:45 pm'.
    18. present: Gives 'approx. 7:45 pm'.
    19. present: Gives 'approx. 7:45 pm'.
    20. present: 'approx. 7:45 pm' given.
    21. present: Gives 'At approx. 7:45 pm'.
    22. present: 'At approx. 7:45 pm'.
    23. present: Gives 'approx. 7:45 pm'.
    24. present: At approx. 7:45 pm.
    25. present: Gives "approx. 7:45 pm".
  • Impactabsent12/25

    Final assessment

    Reads split closely: about half count 'Victim transported to WMC' and 'was stabbed' as stated harm, while a similar-sized group notes the message explicitly says 'no ongoing threat' with no forward-looking severity. The split is essentially even, but slightly more reads lean toward no stated consequence, so the call is absent.

    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. present: States 'no ongoing threat' but victim was 'stabbed' and 'transported to WMC', conveying harm.
    2. absent: No statement of potential harm or severity is included.
    3. absent: States 'There is no ongoing threat', no stated potential harm to recipients.
    4. present: States 'One person...was stabbed' and 'Victim transported to WMC'.
    5. absent: States 'no ongoing threat', no stated potential harm beyond the stabbing itself.
    6. present: "Victim transported to WMC", stabbing injury conveyed.
    7. absent: No statement of potential harm or severity beyond the facts.
    8. absent: States 'There is no ongoing threat', no stated potential harm to recipients.
    9. present: "Victim transported to WMC" and "was stabbed" convey harm to person.
    10. absent: No stated forward consequence; explicitly notes no ongoing threat.
    11. absent: States victim transported to hospital but this describes an outcome not a warned-of potential consequence; no forward-looking harm stated.
    12. present: One person was stabbed and transported to WMC, a stated harm.
    13. present: States victim was stabbed and transported to WMC.
    14. absent: States "no ongoing threat"; victim transported but no explicit severity/risk statement.
    15. present: 'Victim transported to WMC' conveys medical consequence.
    16. present: 'Victim transported to WMC'
    17. absent: States 'There is no ongoing threat', no stated potential harm to reader beyond the stabbing fact itself.
    18. absent: States 'no ongoing threat', no stated potential harm to recipients.
    19. absent: States 'no ongoing threat', no stated future harm.
    20. present: States 'One person... was stabbed' and 'Victim transported to WMC'.
    21. absent: States 'no ongoing threat', victim transported but no severity described.
    22. present: 'One person... was stabbed', victim transported to hospital.
    23. absent: States 'There is no ongoing threat', reporting resolution not potential harm.
    24. present: Victim was transported to WMC after being stabbed.
    25. present: States victim was "stabbed" and "transported to WMC".

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

About this analysis
Context

Background

At approximately 7:45 PM EDT on Friday, April 10, 2026, 19-year-old Guilliani Olguin Jacinto was stabbed at the Lincoln Tower turf fields on Ohio State's campus by a 15-year-old. Police took the suspect into custody within minutes, and Jacinto was transported to the OSU Wexner Medical Center where he was pronounced dead at 12:37 AM EDT on April 11. Despite the fatal attack happening adjacent to one of OSU's largest residence halls, the university did not send a Buckeye Alert; OSU Emergency Management posted on Twitter/X at 8:47 PM EDT and OSU Police followed five minutes later. University spokesperson Dan Hedman explained that 'with the suspect in custody, there was no ongoing threat and therefore no Buckeye Alert was issued.' Students criticized the lack of notification, with many learning of the incident through Snapchat stories. Neither the victim nor the suspect was affiliated with OSU. The 15-year-old was charged with murder and tampering with evidence, and defense counsel argued the stabbing was self-defense. OSU subsequently announced earlier closure of the turf fields and is reviewing structural and technological security upgrades.
Analysis

Key Findings

The incident is a high-profile example of OSU's interpretation of Clery Act 'ongoing threat', fast suspect apprehension was treated as ground for no Buckeye Alert despite a fatality
Students argued that the absence of a formal alert violated their reasonable expectations of being notified about deadly campus violence
OSU's reliance on social media in lieu of Buckeye Alert highlights the gap between Clery's legal minimum (ongoing threat) and community expectations of full transparency
Both victim and suspect were unaffiliated with OSU, illustrating the challenge of campus crime committed by non-students on campus property
Outcome
The 19-year-old victim, Guilliani Olguin Jacinto, was pronounced dead at the OSU Wexner Medical Center at 12:37 AM EDT on April 11. The 15-year-old suspect was charged with murder and tampering with evidence; defense counsel claimed self-defense.
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. Student Paper
    19-year-old man identified in stabbing on Lincoln Field (The Lantern)
    thelantern.com
    archived copy
  2. News
    Ohio State students disappointed over lack of notification following deadly stabbing (WOSU)
    wosu.org
    archived copy
  3. News
    Teen homicide suspect in custody minutes after fatal campus stabbing (10TV)
    10tv.com
    archived copy
  4. News
    Man fatally stabbed at Ohio State turf fields identified (NBC4)
    nbc4i.com
    archived copy
  5. News
    15-year-old charged with murder for stabbing on college campus soccer field (Fox 8)
    fox8live.com
    archived copy
  6. Social
    @OSU_EMFP X — Lincoln Tower stabbing initial notice
    x.com
    archived copy
  7. Social
    @OSU_EMFP X — victim deceased update
    x.com
    archived copy
  8. Social
    @OSUPOLICE X — Lincoln Tower stabbing (mirror)
    x.com
    archived copy
Cite this case

Campus Alert Archive. "The Ohio State University: Stabbing, April 10, 2026." Incident of April 10, 2026. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/ohio-state-lincoln-tower-fatal-stabbing-2026-04-10/

Download case JSON

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

Tags
stabbingfatalohio-statepublic-r1no-alert-issuedsocial-media-notificationclery-controversynon-student-victim
Added May 2026Updated July 2026Via ingestion