Campus Alert Archive
USC

Robbery at 2912 Figueroa Street

AI-generated · every claim is source-linked
CArobberytimely warninghigh confidence
Compare →
Under Investigation

USC Department of Public Safety published a crime alert. Full text recovered from dps.usc.edu.

Alerts
1
Response
—
Killed
—
Injured
—
Institution
University of Southern California
Private R1 · CA
All USC cases →
~49,000 studentsTrojansAlert
Official alert policy
Read when and how USC says it will use TrojansAlert: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

1 message in sequence · 1 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 ALERTEmail
Verified verbatim4646 chars
Incident Description: The suspect approached the first victim who was standing outside the Carl's Jr. He reached into the victim's pocket and took some property. The suspect then approached the second victim who was sitting inside his car in the drive through line. The suspect demanded the victim's wristwatch. After a brief argument, the victim gave his watch to the suspect. The suspect returned to his vehicle and drove away. Reported Offense: Robbery Date & Time of Occurrence: 03/06/2026 4:00 am Location: 2912 Figueroa Street Report Number: 2600859 Vehicle Description: Mercedes SUV, black Suspect Description (provided by reporting party): Age:25 years oldEye Color:UnknownHair Color:UnknownHeight:5'10"Race:HispanicSex:MaleWeight:180 poundsAdditional Description:The suspect was wearing a green hoody.Weapon:None If you are in immediate DANGER, call the Los Angeles Police Department at 911 or the USC Department of Public Safety at (213) 740-4321. Please note that race, ethnicity, gender and/or religious affiliation are NOT considered the basis for suspicion; only behaviors are considered suspicious. If you have any questions or information relevant to the crime(s) reflected in this alert, immediately call DPS at (213) 740-6000 for the University Park Campus (UPC), (323) 442-1000 for the Health Sciences Campus (HSC) or (213) 485-6571 for the LAPD Southwest Division. The purpose of this warning is to aid in the prevention of similar crimes by alerting the community about the incident and to provide information which allows individuals to make informed decisions about their personal safety. USC Department of Public Safety Recommendations - Robbery - Not every person you meet has good intentions. Be cautious of strangers and keep a safe distance. There is safety in numbers, so travel with friends. - Avoid using cell phones or other technology while walking as criminals target distracted, inattentive individuals using them. - If you are the victim of a robbery remain calm and do not resist. Assure the robber you will cooperate and take no action that may jeopardize your safety. Do not make any quick or unexpected movements. Follow the robber's direction, but do not offer more than they ask for. Don't argue with the robber. - After the robbery, go immediately to a safe location and report the crime to law enforcement . Call DPS emergency for UPC at (213) 740-4321, for HSC call (323) 442-1000 or call 911 for LAPD. - If you observe a crime in progress, STAY CALM AND CALL DPS emergency for UPC at (213) 740-4321, for HSC call (323) 442-1000 or call 911 for LAPD. - Be a good witness : It is important to recall what you observed and provide as many details as possible to law enforcement such as: the sex, race, age, height, hair color, clothing, tattoos, scars of any suspects and a description of the make and model of any vehicle used in the crime and its license plate if possible. - Do not attempt to apprehend any suspects or perpetrators of crime. For other options to contact DPS, report crime, and ask for help, please visit USC DPS Report a Crime. USC Transportation provides options to travel around USC including the Lyft Rides Program: - Get a Ride: Lyft is available at HSC and UPC to cover shared rides. Lyft at UPC is open from 7 p.m. to 2 a.m. seven days a week (*on home football game days, the program begins 5 hours after scheduled kickoff) . Lyft at HSC is open from 5 p.m. to 2 a.m., Monday through Friday only. Please visit the USC Lyft page for more information. - Verify your driver and car: Once you have requested a Lyft ride, you can view the driver's rating. When your ride arrives, make sure the driver's photo, license plate number, and vehicle description match. Never take a ride you did not request or get into a car that doesn't match the details provided by the Lyft app. - Go the extra mile: The Lyft app's "share your ETA" function allows you to invite friends to see your trip in real-time. The app will draft a text message you can share with friends that includes your ETA and a link to a live map that allows them to track your trip. Too much effort? Call a friend and stay on the line while you're in the car instead. To receive more information from USC DPS, please register for TrojansAlert: - TrojansAlert: Register for USC's emergency notification system TrojansAlert to allow university officials to contact you during an emergency by sending messages via text message and email. (Please note that students, staff and faculty automatically are signed up for TrojansAlerts. For additional USC Resources, please visit USC Report & Response.
Verify this quote
USC DPS official crime alert pagedps.usc.edufind archived copies
Verbatim from official dps.usc.edu crime alert page.
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.

Incident Description: The suspect approached the first victim who was standing outside the Carl's Jr. He reached into the victim's pocket and took some property. The suspect then approached the second victim who was sitting inside his car in the drive through line. The suspect demanded the victim's wristwatch. After a brief argument, the victim gave his watch to the suspect. The suspect returned to his vehicle and drove away. Reported Offense: Robbery Date & Time of Occurrence: 03/06/2026 4:00 am Location: 2912 Figueroa Street Report Number: 2600859 Vehicle Description: Mercedes SUV, black Suspect Description (provided by reporting party): Age:25 years oldEye Color:UnknownHair Color:UnknownHeight:5'10"Race:HispanicSex:MaleWeight:180 poundsAdditional Description:The suspect was wearing a green hoody.Weapon:None If you are in immediate DANGER, call the Los Angeles Police Department at 911 or the USC Department of Public Safety at (213) 740-4321. Please note that race, ethnicity, gender and/or religious affiliation are NOT considered the basis for suspicion; only behaviors are considered suspicious. If you have any questions or information relevant to the crime(s) reflected in this alert, immediately call DPS at (213) 740-6000 for the University Park Campus (UPC), (323) 442-1000 for the Health Sciences Campus (HSC) or (213) 485-6571 for the LAPD Southwest Division. The purpose of this warning is to aid in the prevention of similar crimes by alerting the community about the incident and to provide information which allows individuals to make informed decisions about their personal safety. USC Department of Public Safety Recommendations - Robbery - Not every person you meet has good intentions. Be cautious of strangers and keep a safe distance. There is safety in numbers, so travel with friends. - Avoid using cell phones or other technology while walking as criminals target distracted, inattentive individuals using them. - If you are the victim of a robbery remain calm and do not resist. Assure the robber you will cooperate and take no action that may jeopardize your safety. Do not make any quick or unexpected movements. Follow the robber's direction, but do not offer more than they ask for. Don't argue with the robber. - After the robbery, go immediately to a safe location and report the crime to law enforcement . Call DPS emergency for UPC at (213) 740-4321, for HSC call (323) 442-1000 or call 911 for LAPD. - If you observe a crime in progress, STAY CALM AND CALL DPS emergency for UPC at (213) 740-4321, for HSC call (323) 442-1000 or call 911 for LAPD. - Be a good witness : It is important to recall what you observed and provide as many details as possible to law enforcement such as: the sex, race, age, height, hair color, clothing, tattoos, scars of any suspects and a description of the make and model of any vehicle used in the crime and its license plate if possible. - Do not attempt to apprehend any suspects or perpetrators of crime. For other options to contact DPS, report crime, and ask for help, please visit USC DPS Report a Crime. USC Transportation provides options to travel around USC including the Lyft Rides Program: - Get a Ride: Lyft is available at HSC and UPC to cover shared rides. Lyft at UPC is open from 7 p.m. to 2 a.m. seven days a week (*on home football game days, the program begins 5 hours after scheduled kickoff) . Lyft at HSC is open from 5 p.m. to 2 a.m., Monday through Friday only. Please visit the USC Lyft page for more information. - Verify your driver and car: Once you have requested a Lyft ride, you can view the driver's rating. When your ride arrives, make sure the driver's photo, license plate number, and vehicle description match. Never take a ride you did not request or get into a car that doesn't match the details provided by the Lyft app. - Go the extra mile: The Lyft app's "share your ETA" function allows you to invite friends to see your trip in real-time. The app will draft a text message you can share with friends that includes your ETA and a link to a live map that allows them to track your trip. Too much effort? Call a friend and stay on the line while you're in the car instead. To receive more information from USC DPS, please register for TrojansAlert: - TrojansAlert: Register for USC's emergency notification system TrojansAlert to allow university officials to contact you during an emergency by sending messages via text message and email. (Please note that students, staff and faculty automatically are signed up for TrojansAlerts. For additional USC Resources, please visit USC Report & Response.

  • Sourcepresent25/25

    Final assessment

    USC Department of Public Safety is the named 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: USC Department of Public Safety is the named sender. Independent review agrees.
    2. present: USC Department of Public Safety is the named sender. Confirmed on re-read.
    3. present: USC Department of Public Safety is the named sender. Based solely on the alert text.
    4. present: USC Department of Public Safety is the named sender. From the full message only.
    5. present: USC Department of Public Safety is the named sender. No outside context used.
    6. present: USC Department of Public Safety is the named sender. Strict rubric application.
    7. present: USC Department of Public Safety is the named sender. Element coded from wording alone.
    8. present: USC Department of Public Safety is the named sender. Same conclusion on second look.
    9. present: USC Department of Public Safety is the named sender. Matches the public-warning test.
    10. present: USC Department of Public Safety is the named sender. Wording is decisive here.
    11. present: USC Department of Public Safety is the named sender. Clear institutional sender cue.
    12. present: USC Department of Public Safety is the named sender. Source attribution is explicit.
    13. present: USC Department of Public Safety is the named sender. Sender language is unambiguous.
    14. present: USC Department of Public Safety is the named sender. Reads as official campus channel.
    15. present: USC Department of Public Safety is the named sender. No ambiguity on who issued it.
    16. present: USC Department of Public Safety is the named sender. Judged present from named agency.
    17. present: USC Department of Public Safety is the named sender. Agency or office is named.
    18. present: USC Department of Public Safety is the named sender. Public safety sender is clear.
    19. present: USC Department of Public Safety is the named sender. Official notice framing supports source.
    20. present: USC Department of Public Safety is the named sender. Source element satisfies the bar.
    21. present: USC Department of Public Safety is the named sender. Re-checked against full paragraph.
    22. present: USC Department of Public Safety is the named sender. Pass agrees with majority logic.
    23. present: USC Department of Public Safety is the named sender. Source present in opening framing.
    24. present: USC Department of Public Safety is the named sender. Institutional voice is obvious.
    25. present: USC Department of Public Safety is the named sender. Final independent coding concurs.
  • Hazardpresent25/25

    Final assessment

    Attempted robbery is the named 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: Attempted robbery is the named hazard. Hazard is specifically named.
    2. present: Attempted robbery is the named hazard. The danger is explicit in text.
    3. present: Attempted robbery is the named hazard. Crime or condition is identified.
    4. present: Attempted robbery is the named hazard. Named incident type is the hazard.
    5. present: Attempted robbery is the named hazard. Clear what recipients should fear.
    6. present: Attempted robbery is the named hazard. Hazard language is concrete.
    7. present: Attempted robbery is the named hazard. Not merely a generic notice.
    8. present: Attempted robbery is the named hazard. Incident type is stated outright.
    9. present: Attempted robbery is the named hazard. Risk is identified by name.
    10. present: Attempted robbery is the named hazard. Threat type is readable on face.
    11. present: Attempted robbery is the named hazard. Hazard element meets the bar.
    12. present: Attempted robbery is the named hazard. Confirmed from full alert wording.
    13. present: Attempted robbery is the named hazard. Independent pass finds hazard present.
    14. present: Attempted robbery is the named hazard. Event described is the hazard.
    15. present: Attempted robbery is the named hazard. No need for outside knowledge.
    16. present: Attempted robbery is the named hazard. Re-read supports hazard present.
    17. present: Attempted robbery is the named hazard. Specific harm pathway is stated.
    18. present: Attempted robbery is the named hazard. Alert centers on a named problem.
    19. present: Attempted robbery is the named hazard. Hazard coding is straightforward.
    20. present: Attempted robbery is the named hazard. Wording alone decides this.
    21. present: Attempted robbery is the named hazard. Same call on second review.
    22. present: Attempted robbery is the named hazard. Hazard present by majority test.
    23. present: Attempted robbery is the named hazard. Distinct from mere logistics.
    24. present: Attempted robbery is the named hazard. Public-warning hazard test passed.
    25. present: Attempted robbery is the named hazard. Final independent coding concurs.
  • Locationpresent25/25

    Final assessment

    A specific street, block, or campus location is named.

    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: A specific street, block, or campus location is named. Place detail is specific enough.
    2. present: A specific street, block, or campus location is named. Location cue is usable on campus.
    3. present: A specific street, block, or campus location is named. Named place supports location present.
    4. present: A specific street, block, or campus location is named. Address or area is explicit.
    5. present: A specific street, block, or campus location is named. Recipients can locate the scene.
    6. present: A specific street, block, or campus location is named. Geographic detail is in the text.
    7. present: A specific street, block, or campus location is named. Location element meets the bar.
    8. present: A specific street, block, or campus location is named. Not just a vague campus-wide label.
    9. present: A specific street, block, or campus location is named. Independent re-read agrees.
    10. present: A specific street, block, or campus location is named. Place is coded from wording alone.
    11. present: A specific street, block, or campus location is named. Specific block or building appears.
    12. present: A specific street, block, or campus location is named. Location is concrete in the alert.
    13. present: A specific street, block, or campus location is named. Scene is spatially identifiable.
    14. present: A specific street, block, or campus location is named. Map-level detail is present.
    15. present: A specific street, block, or campus location is named. Location present under the rubric.
    16. present: A specific street, block, or campus location is named. Same judgment on second look.
    17. present: A specific street, block, or campus location is named. Place language is decisive.
    18. present: A specific street, block, or campus location is named. No outside context required.
    19. present: A specific street, block, or campus location is named. Named site is clear.
    20. present: A specific street, block, or campus location is named. Location coding is straightforward.
    21. present: A specific street, block, or campus location is named. Pass finds location present.
    22. present: A specific street, block, or campus location is named. Geographic anchor is sufficient.
    23. present: A specific street, block, or campus location is named. Location test satisfied.
    24. present: A specific street, block, or campus location is named. Wording alone settles location.
    25. present: A specific street, block, or campus location is named. Final independent coding concurs.
  • Guidancepresent25/25

    Final assessment

    Protective actions and reporting instructions are present.

    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: Protective actions and reporting instructions are present. Protective action is stated.
    2. present: Protective actions and reporting instructions are present. Recipients are told what to do.
    3. present: Protective actions and reporting instructions are present. Clear call-to-action guidance.
    4. present: Protective actions and reporting instructions are present. Guidance is actionable on its face.
    5. present: Protective actions and reporting instructions are present. Safety steps are listed or implied as directives.
    6. present: Protective actions and reporting instructions are present. Report/call instructions count as guidance.
    7. present: Protective actions and reporting instructions are present. Avoidance or vigilance language is present.
    8. present: Protective actions and reporting instructions are present. Guidance element meets the bar.
    9. present: Protective actions and reporting instructions are present. Independent re-read agrees.
    10. present: Protective actions and reporting instructions are present. Instructional language is explicit.
    11. present: Protective actions and reporting instructions are present. Readers know how to respond.
    12. present: Protective actions and reporting instructions are present. Protective guidance is concrete.
    13. present: Protective actions and reporting instructions are present. Action cues are in the alert.
    14. present: Protective actions and reporting instructions are present. Same conclusion on second look.
    15. present: Protective actions and reporting instructions are present. Guidance coded from wording alone.
    16. present: Protective actions and reporting instructions are present. No outside context required.
    17. present: Protective actions and reporting instructions are present. Directive phrasing is clear.
    18. present: Protective actions and reporting instructions are present. Guidance present under the rubric.
    19. present: Protective actions and reporting instructions are present. Pass finds guidance present.
    20. present: Protective actions and reporting instructions are present. Public-warning guidance test passed.
    21. present: Protective actions and reporting instructions are present. Recipients get do/don't instructions.
    22. present: Protective actions and reporting instructions are present. Contact numbers support guidance.
    23. present: Protective actions and reporting instructions are present. Wording alone settles guidance.
    24. present: Protective actions and reporting instructions are present. Strict application still finds guidance.
    25. present: Protective actions and reporting instructions are present. Final independent coding concurs.
  • Timepresent25/25

    Final assessment

    Date and time of occurrence are stated.

    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: Date and time of occurrence are stated. Time or date cue is usable.
    2. present: Date and time of occurrence are stated. Clock or calendar detail is present.
    3. present: Date and time of occurrence are stated. Timing of the event is stated.
    4. present: Date and time of occurrence are stated. Time window is specific enough.
    5. present: Date and time of occurrence are stated. Date stamp supports time present.
    6. present: Date and time of occurrence are stated. Independent re-read agrees.
    7. present: Date and time of occurrence are stated. Time element meets the bar.
    8. present: Date and time of occurrence are stated. Not merely undated prose.
    9. present: Date and time of occurrence are stated. Temporal anchor is in the text.
    10. present: Date and time of occurrence are stated. Recipients can place when it happened.
    11. present: Date and time of occurrence are stated. Time coding is straightforward.
    12. present: Date and time of occurrence are stated. Same judgment on second look.
    13. present: Date and time of occurrence are stated. Wording alone settles time.
    14. present: Date and time of occurrence are stated. Pass finds time present.
    15. present: Date and time of occurrence are stated. Explicit hour or day appears.
    16. present: Date and time of occurrence are stated. Temporal detail is operational.
    17. present: Date and time of occurrence are stated. Time present under the rubric.
    18. present: Date and time of occurrence are stated. No outside context required.
    19. present: Date and time of occurrence are stated. Date/time language is decisive.
    20. present: Date and time of occurrence are stated. Calendar cue is clear.
    21. present: Date and time of occurrence are stated. Timing is not vague.
    22. present: Date and time of occurrence are stated. Time test satisfied.
    23. present: Date and time of occurrence are stated. Re-checked against full text.
    24. present: Date and time of occurrence are stated. Strict rubric still finds time.
    25. present: Date and time of occurrence are stated. Final independent coding concurs.
  • Impactpresent25/25

    Final assessment

    Realized harm, loss, or ongoing risk is 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. present: Realized harm, loss, or ongoing risk is described. Impact or status is described.
    2. present: Realized harm, loss, or ongoing risk is described. Consequences or outcome appear.
    3. present: Realized harm, loss, or ongoing risk is described. Severity or scope is stated.
    4. present: Realized harm, loss, or ongoing risk is described. Harm already realized is noted.
    5. present: Realized harm, loss, or ongoing risk is described. Operational impact is explicit.
    6. present: Realized harm, loss, or ongoing risk is described. Status language supports impact.
    7. present: Realized harm, loss, or ongoing risk is described. Impact element meets the bar.
    8. present: Realized harm, loss, or ongoing risk is described. Independent re-read agrees.
    9. present: Realized harm, loss, or ongoing risk is described. Effects on people or systems appear.
    10. present: Realized harm, loss, or ongoing risk is described. Not hazard alone; impact is separate.
    11. present: Realized harm, loss, or ongoing risk is described. Same conclusion on second look.
    12. present: Realized harm, loss, or ongoing risk is described. Wording alone settles impact.
    13. present: Realized harm, loss, or ongoing risk is described. Pass finds impact present.
    14. present: Realized harm, loss, or ongoing risk is described. Outcome or threat-level is clear.
    15. present: Realized harm, loss, or ongoing risk is described. Impact coded from wording alone.
    16. present: Realized harm, loss, or ongoing risk is described. No outside context required.
    17. present: Realized harm, loss, or ongoing risk is described. Public-warning impact test passed.
    18. present: Realized harm, loss, or ongoing risk is described. Scope of disruption is given.
    19. present: Realized harm, loss, or ongoing risk is described. Status update implies impact.
    20. present: Realized harm, loss, or ongoing risk is described. Realized or potential harm is named.
    21. present: Realized harm, loss, or ongoing risk is described. Impact language is concrete.
    22. present: Realized harm, loss, or ongoing risk is described. Re-checked against full alert.
    23. present: Realized harm, loss, or ongoing risk is described. Strict rubric still finds impact.
    24. present: Realized harm, loss, or ongoing risk is described. Impact present under majority logic.
    25. present: Realized harm, loss, or ongoing risk is described. Final independent coding concurs.

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

About this analysis
Context

Background

Official USC Department of Public Safety crime alert archive.
Analysis

Key Findings

Complete official DPS crime alert text recovered.
Outcome
See official DPS crime alert for investigation status and safety guidance.
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
    Robbery at 2912 Figueroa Street
    dps.usc.edu
    archived copy
Cite this case

Campus Alert Archive. "University of Southern California: Robbery at 2912 Figueroa Street." Incident of March 6, 2026. Added July 2026. https://campusalertarchive.com/case/university-of-southern-california-robbery-168-2026-03-06/

Download case JSON

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

Tags
usc2026robberydpscleryUnder Investigation
Added July 2026Updated July 2026Via ingestion