Questions & answers

What we know. The reviewed recording includes Bittony saying there was no translator there and that he would try speaking with Shubham. An earlier request is also documented in the GPD recording.

Translator and language record

What would answer it. Identify the assistance available, attempted or ruled out, and whether GPD communicated the earlier request during the handoff.

What we know. The language review identifies a misunderstanding of a basic bus-origin question and later exchanges showing difficulty understanding. These observations do not establish a formal language-proficiency level.

Translator and language record

What would answer it. Explain how comprehension of the allegation was assessed and how the need for qualified interpretation was evaluated.

What we know. The timestamp review identifies six generic formulations. It also acknowledges the later buttocks-specific wording at 28:31. The explicit four-contact count and full progression of the reported contact were not clearly carried into the questioning.

The six formulations

What would answer it. Explain the wording choices and identify where the complete allegation was put to Shubham.

What we know. The published timestamp review identifies no clear presentation of the complete allegation in the recording reviewed. This is a finding limited to that reviewed material.

How the allegation was phrased

What would answer it. Identify any other recording or documented interpreted interview that presents the complete allegation and preserves Shubham’s response.

What we know. The published comparison identifies ten moments when Bittony supplied or reinforced possible explanations, with the speaker and timestamp for each.

The ten explanations

What would answer it. Identify the evidence supporting each suggestion and explain how the answers affected the investigation. Considering alternatives alone does not resolve this question.

What we know. The review distinguishes Shubham’s answers from the later helper’s answers and identifies explanations repeated after rejection. The source of the seat-space explanation matters.

Suggestions and recorded responses

What would answer it. Explain why particular suggestions continued, who supported them, and how rejected explanations were documented.

What we know. The published review identifies nine reassurances or minimizing statements during the interview. Each is linked to a recording cue.

The nine reassurances

What would answer it. Explain how those statements were reconciled with investigative steps that remained outstanding.

What we know. At 34:47 Bittony says Shubham will not go to jail; at 34:52 he says he has to gather all the evidence. The later court filing does not establish what decision had already been made at that moment.

The five-second comparison

What would answer it. Identify the decision made at that point, its basis, and the evidence still to be gathered.

What we know. The reviewed on-scene exchange identifies no payment demand by the female passenger. The helper’s suggestion and Bittony’s responses are identified separately. A later refund or liability claim does not establish a basis for the roadside speculation.

Money and fraud discussion

What would answer it. Identify what on-scene evidence supported the money or insurance-fraud suggestion.

What we know. The report records identifying information. GPD said on September 4 that its agency conducted no NCIC inquiry for this incident; that statement does not establish what MCSO did.

Identity and locating record · GPD’s September 4 response

What would answer it. Identify MCSO’s independent checks and how it reconciled conflicting name or identity entries.

What we know. The released GPD notes contain identifying information, and the complaint lists a government-ID reference. Seeing, recording, photographing and independently verifying a document are different actions.

Recorded identification information · GPD’s stated limits

What would answer it. Identify the document each deputy examined or copied and the checks performed against it.

What we know. The record contains identifying information and statements about country of origin. Neither alone establishes the completeness of identity verification.

Identity and verification notes

What would answer it. Identify what was established from the identification presented, how name discrepancies were reconciled, and which case-related verification procedures applied.

What we know. The report and September 10 summons contain locating information. Bernitz’s September 10 email acknowledges uncertainty about the apartment unit. Recording an address is different from verifying it.

Locating record · September DA correspondence

What would answer it. Identify what address, contact information and destination MCSO verified before departure, and any later corrections.

What we know. On September 1 Bernitz described asking the deputy to file a summons. The September 10 summons includes a mailing certificate. That records mailing, not actual receipt or the plan in place when Shubham left Gallup.

September DA chronology · Filing and summons

What would answer it. Provide the release-time locating plan, address-verification history and any delivery or service record.

What we know. The recording captures discussion of asking nearby passengers. The report contains no accounts from those other passengers. Later Gallagher Bassett witness outreach does not establish that MCSO completed interviews.

Recorded witness discussion · Later claims outreach

What would answer it. List the nearby passengers MCSO identified, contacted or interviewed, with dates and the resulting statements.

What we know. The driver’s recorded account and refusal to reboard Shubham can be compared with the report. On September 16 Drake corrected her own seating-attribution account; that is a claims response, not a correction to MCSO’s report.

Report and recording comparison · Claims seating clarification

What would answer it. Reconcile the driver’s recorded words and actions with the report, and identify any correction or supplemental account.

What we know. The removal is documented in the report, and the recording captures the refusal to reboard Shubham. Greyhound incident GH034799 is identified in the report.

Documented driver response · MCSO report comparison

What would answer it. Identify who made the company decision, its documented basis, and how MCSO considered that basis.

What we know. The comparison identifies omissions from the original report, including the explicit four-contact count and seat-position context. The original report and reproduced September 9 DA narrative retain the continued-touching passage; the September 10 complaint omits it. The driver paragraph still includes private-area wording.

Compare the passages · Intermediate narrative · Complaint preparation question

October 1 review. The October 1 supplement to IPRA #10 seeks the native narrative, draft complaint and version history needed to explain this change. The request does not establish who edited the passage. Read the dated update.

What would answer it. Explain the original omissions and the further complaint change, with drafts, supplements and the review history. Q49 separately tracks complaint preparation.

What we know. On September 17, MCSO’s #10 response said there were no new responsive records, attached the DA email/narrative and criminal complaint, and closed the request. That production response is not proof that no supplement was ever created.

September 17 response and attachments · Earlier disputed records

October 1 review. On October 1 the passenger renewed the existing request for drafts, revisions, native files and audit history. September 17’s no-new-records statement does not establish that drafts never existed or explain the wording change. Read the dated update.

What would answer it. Identify any supplements or revision records and the repositories, custodians and time periods searched.

What we know. The report names Savannah Benally as reviewer; Maiorano’s August 21 email describes her approval. Produced Policy 323.6 addresses content and accuracy review, but its operative version on July 16 still needs confirmation.

Named reviewer and record · Policy and review comparison

What would answer it. Identify what Benally reviewed, when, and any correction or approval records.

What we know. The later camera audits identify viewing and export events. They do not establish Benally’s review of the underlying evidence before report approval.

Named audit entries · Benally’s role and recordings

What would answer it. Provide a dated review trail for the report, bodycam, CAD and audio, including any shared or exported copies.

What we know. Maiorano’s August 21 email calls the investigation sufficient and cites misdemeanor battery, no physical evidence and no admission. His stated rationale is a response; its application to the identified gaps remains unresolved.

Policy and case comparison · August 21 response

What would answer it. Explain how the applicable investigative standards were applied to the witness, language, report and evidence gaps.

What we know. Maiorano said on August 21 that he reviewed the report and video. None of the four supplied audit PDFs contains a Viewed entry under his name. Shared or exported viewing remains possible.

Statement and named-access comparison · Sheriff’s review statement

October 13 review. The October 12 request now separately seeks review documentation, system access records and any review using exported copies. No response was located through October 13. Read the request summary.

What would answer it. Identify his viewing method and dates, the material compared, and how he addressed the discrepancies.

What we know. Command-review correspondence already exists. MCSO’s September 17 #7 reply reports no responsive case-specific records; the broader historical portion remains in additional-time processing.

Request #7 response · Known access records

October 13 review. MCSO’s September 29 letter acknowledges NMDOJ’s correspondence and says it will be filed with the case. NMDOJ’s October 6 response describes the matter as under review; the MCSO letter itself supplies no review assignment or findings. Compare both letters.

What would answer it. Identify the case-review disposition and explain which complaint, review and corrective-action repositories were searched.

What we know. MCSO answered the January 19–23, 2026 BATI attendance question on August 21: “Deputy Bittony did not attend the class.” That narrow answer does not establish his complete training history or other staff’s attendance.

August 21 training answer · Training-request history

What would answer it. Provide Bittony’s relevant course history, qualifications and any later remedial training.

What we know. The site publishes five core policies from the production. Their text can be compared with the case, but production alone establishes neither compliance nor which version governed on July 16.

Policy and record comparison · Version and procedure gaps

What would answer it. Identify the operative policies and the case-specific compliance review, with the supporting evidence.

What we know. MCSO reported an August transmission. On September 1 Bernitz said he had been unaware GPD responded and lacked the female officer’s video. The September 9 email documents a Word-narrative transmission; filing followed September 10. September 9 is not established as the first transmission of anything.

September emails and narrative · Earlier referral record

October 1 review. The October 1 supplement specifically seeks the request preceding the September 9 email’s “As requested Sir” wording, related communications, and the native Word attachment. The reproduced attachment text does not establish the complete transmission chain. Read the dated update.

What would answer it. Provide an itemized sent, received and reviewed timeline for each report, recording, note and narrative version.

What we know. Prosecutor correspondence, the September 9 narrative email and the September 10 filing document later activity. MCSO’s September 17 #10 response supplies the email and complaint without a further investigative-work history.

Documented later activity · Request #10 response

October 1 review. The October 1 supplement seeks September 9–10 preparation, approval, filing and version records. No agency answer to that supplement is included in this review. Read the dated update.

What would answer it. Identify additional MCSO interviews, evidence acquisition and corrections after July 16, with dates and resulting records.

What we know. MCSO correspondence and records responses exist. The DA separately communicated on September 1 and September 10, including a promise to report developments. Those communications do not answer what proactive MCSO case follow-up occurred.

MCSO correspondence · Separate DA communications

What would answer it. Provide dated MCSO case-status, evidence-follow-up and victim-support communications and identify the responsible staff.

What we know. This overlaps Q22, which contains the Sheriff’s stated rationale and the policy comparison. The original question number and discussion remain available here.

Read the main sufficiency question · Compare the policies and case

What would answer it. Address the specific unresolved investigative steps identified in Q22 and the linked comparison.

What we know. The August 21 email imposes the AI-related condition. On September 17, the #9 response referred to an already-provided email and policy, supplied no new responsive records, and closed the request.

August 21 condition · Request #9 response

What would answer it. Identify the particular policy relied on and explain how it justified conditioning substantive conversation on drafting assistance.

What we know. The August 25 internal email identifies Chief Deputy Eric Jim as the routing recipient. That answers where staff were told to send the emails.

August 25 instruction · Subsequent responses

October 1 review. The September 28 processing notice says September 24–28 requests were added to pending requests for production in order received, without a fixed next date. It does not supply the case-specific assignment trail. Read the dated update.

What would answer it. Identify which investigative concerns, new evidence, service requests and records requests were assigned, acted on or answered after routing.

What we know. September 3 and September 17 responses report no responsive or no new responsive records in specified categories. Other categories refer to earlier productions or remain in additional-time processing. A production response does not establish whether the underlying activity occurred.

September 17 request-by-request status · Earlier responses and disputed searches

October 1 review. A September 28 response on IPRA authority and assignment directs the requester to the county custodian listing, says there are no other responsive records, and closes that request. It does not explain the searches or internal assignment and prioritization decisions. Read the dated update.

What would answer it. Provide category-specific search scope, custodians and dates, and identify each record described as already provided.

What we know. Jim apologized on September 10 for using a records-response template for the evidence follow-up. GPD’s September 4 response says it did not know the person in the supplied photograph. Neither response documents acquisition of the ticket photograph or identification of the device.

Jim’s apology and follow-up · GPD’s response

What would answer it. Identify who pursued the photograph and person/device, the preservation steps, and the resulting evidence.

What we know. The September 11 notice counted 56 remaining requests at that time. Later responses close #9 and #10, split #7 and #11, and answer #8’s categories 1–7. September 16 and 18 notices add newer requests to pending processing. The current balance is not established by the earlier count.

September 17 status table · Later additional-time notices

October 1 review. Through October 1, the record also includes September 28’s open-ended processing notice and separate authority-request closure, the September 30 follow-up on Jim’s promised response for separate incident 25-3311, and the October 1 supplement to IPRA #10. A reconciled current request-by-request inventory is still needed; the earlier totals are historical. Read the dated update.

October 13 review. October 1 brought a 16-page tracker production and a 15-page NMDOJ packet; both closures were disputed. Eleven located October 9 notices promise rolling production without attachments or a fixed date. New October 11 and 12 requests remain separately tracked. These counts do not establish the current outstanding balance. Read the production review.

What would answer it. Provide a reconciled request inventory showing each scope, production, closure or pending category and next production date.

What we know. Produced letters dated September 14 and 23 address MCSO’s Gallup office and specify U.S. postal service. The first requests receipt confirmation by September 21; the second requests a status response by September 30. An assignment message identifies intake assignee K. Martinez. The letters use an office signature, not an individual decision-maker. The reviewed submission export lists three attachments, but does not establish the exact referral packet or its delivery.

Both referral letters — redacted PDF · September 29 production review

October 13 review. The October 1 production includes a September 29 acknowledgment signed by Maiorano. Receipt is now documented. It says NMDOJ’s correspondence will be added to the case file. NMDOJ’s October 6 response confirms acknowledgment, but the named referral decision-maker and exact transmission packet remain unestablished. Read both letters.

What would answer it. Identify who decided, authored and approved the referral; produce the exact transmitted packet, transmission and receipt records, named MCSO recipient, and any additional response to each letter beyond the acknowledgment now produced. An intake assignment alone does not establish who made the referral decision.

What we know. NMDOJ stated that MCSO was better suited to address the issues. The passenger’s follow-ups seek the review basis and reconsideration process. Separate NMSP and LECB paths are not closed by this NMDOJ email.

NMDOJ’s stated position · Separate oversight paths

October 1 review. The produced September 14 and 23 letters establish a referral letter and follow-up inquiry to MCSO. The assignment message identifies an intake assignee. Neither identifies a substantive independent review or its findings. NMDOJ’s September 29 closure of records request #26-815 is separate from the complaint closure and does not answer this question. Read the dated update.

October 13 review. NMDOJ’s October 6 bureau response gives a stated basis: it found no 15-day-response failure for two earlier requests, attributes administrative officer review to the employer and points to the DA for case records and preservation. It describes MCSO’s September 29 response as indicating review; the produced MCSO letter itself only acknowledges receipt and filing. Neither supplies findings from an independent investigation of the underlying conduct. Read the new response and its limits.

What would answer it. Describe the substantive review supporting the referral and the available supervisory-review or reconsideration process.

What we know. On September 1 Bernitz said he was unaware GPD had responded and would request its information; he also said he lacked the female officer’s video. On September 4 GPD said MCSO had not requested or received its records. This concerns the records handoff, not every possible agency communication.

DA’s September 1 statements · GPD’s September 4 statement

What would answer it. Identify when MCSO and the DA obtained each GPD recording and note, and when each was reviewed.

What we know. Jeanine Drake is identified as a liability claims examiner. Gallagher Bassett’s September 16 correspondence describes claim investigation for Flixbus/Bus Risk Retention Group and acknowledges the passenger’s concerns. It does not identify the owner or findings of a separate company operational safety review.

Identified claims role and responses · Earlier management escalation

What would answer it. Identify who owns that safety review, its scope, evidence, findings and resulting changes.

What we know. On September 16 Drake declined requested internal records and said Gallagher Bassett was not in a position to comment on client or third-party records’ existence, contents, preservation or production. That response neither confirms nor disproves preservation.

September 16 records position · Outstanding company records

What would answer it. Have the responsible custodian account for GH034799, ticket photographs, booking and boarding records, any later transportation, and transfers to law enforcement.

What we know. Page 2 of Benally’s vehicle audit lists the three MP4 streams in an August 18 export inventory, with filenames and hashes. This provides evidence of export, not proof that every stream was delivered to the requester.

Export inventory, page 2 · Disputed video delivery

What would answer it. Map the G-1, G-2 and G-3 filenames and hashes to the supplied files, and account for any undelivered stream.

What we know. The September 15 #4 response reports no responsive records in all eight processing-record categories. The passenger’s September 17 review compares that response with documented processing correspondence and activity.

Eight-category response · Related search-scope question

What would answer it. Explain the search for each requested category and date range, including how the known processing records were treated.

What we know. The logs contain action-specific retention fields including 365 days, 120 days and “Indefinitely.” Those values do not establish current preservation, a complete later history or deletion.

Audit-field guide · Preservation records sought

What would answer it. Explain the field meanings and subsequent history, and identify case-specific preservation instructions, holds and actions.

What we know. Request #6 supplied nine policy attachments; the body-camera policy had been supplied with #5. This site highlights five core policies. The July 29 footers do not establish effective dates.

Policy inventory and version limits · Outstanding procedures

October 13 review. The complete-policy request was sent October 5. Yazzie’s October 9 notice records receipt on October 8 and promises rolling production, without attachments. The October 12 body-camera-review request also seeks operative versions and effective-date records. Read the newer scopes.

What would answer it. Provide operative-version records and account for the referenced interpreter procedures, retention schedule and Protected Information Policy.

What we know. The supplied audits name Harolynn Yazzie in Viewed entries for Bittony’s and Benally’s recordings on September 1. They do not establish viewing duration, purpose or results. Employment information is not evidence of what she did in this case.

Named entries and source audits · Published role information

What would answer it. Identify the assignment, scope of viewing and any resulting review, communication or findings.

What we know. The company correspondence raises differences between travel-record names and the identification presented. Drake says the identity concern will be evaluated. No reconciliation is supplied in the reviewed correspondence; a discrepancy does not establish fraud or motive.

Claims acknowledgment · Company records questions · Separate MCSO verification question

What would answer it. Reconcile the reservation, ticket, boarding and identification records, including what staff checked and how differences were handled.

What we know. The passenger reports being told that July 21 and August 18 replies had been sent, but says she could not find them. The mailbox-search and social-message exhibits support the history of that dispute; they do not prove no messages were sent.

Missing-reply correspondence · Follow-up request

What would answer it. Provide the complete replies and sending or delivery information.

What we know. The open letter reproduces the July 16 VINELink request and reports no reply. The photographed card supplies office contacts and an incident number, but no VINELink instructions. Later court and DA communications do not answer what MCSO did about this request.

Card and July 16 VINELink question · Current court information

What would answer it. Provide MCSO’s response or other documented assistance concerning the July 16 request.

What we know. The original report and reproduced September 9 narrative retain continued touching and immediate confrontation. The September 10 complaint omits that passage and bears Bittony’s signature. Sender and signer are known; the editor and reason are not.

Side-by-side text record · September 9 intermediate narrative

October 1 review. The October 1 IPRA #10 supplement explicitly seeks the preceding DA request, native Word file, drafts, metadata and preparation/approval records. It does not identify an editor or establish that an earlier passenger email caused the change. This question remains open. Read the dated update.

What would answer it. Provide the native Word file, editable complaint, retained drafts, metadata and routing/approval records showing who changed and reviewed the wording.

What we know. The passenger raised the discrepancy on September 17. On September 22–23, Bernitz said he was not concerned, referred to testimony and video at trial, and stated that he did not believe the discrepancy was material. On September 24, he deferred further replies until after October 2. These replies document the prosecutor’s position but do not identify the editor, describe a comparison of the source versions, or document a correction.

Discrepancy and follow-up · September 22–24 DA responses · Separate certification referral

October 1 review. The governor’s September 29 replies provide legal resources and direct the passenger back to the DA; they do not address the wording change on its merits. The October 1 records supplement seeks the missing preparation and review history. Neither documents a correction. Read the dated update.

What would answer it. Identify who changed the wording, what comparison or review supported the prosecutor’s conclusion, whether the court was informed, and any correction, supplement or documented decision not to correct.

What we know. The language review documents later assistance by another person. Produced Policy 332.11 addresses interpreter identification and contact documentation; the operative version remains a separate question.

Recorded language-assistance review · Produced language policy

What would answer it. Identify the helper, language used, qualification assessment and the complete recorded interpretation of the allegation and response.

What we know. On September 10 Major Randy Larcher wrote that he was forwarding the email to NMSP’s Albuquerque criminal-investigations section and that someone would reach out. Forwarding alone does not establish that a criminal investigation was opened.

NMSP’s forwarding response

What would answer it. Provide the recipient or assigned reviewer, matter number, contact history and written disposition after that forwarding.

What we know. LECB acknowledged receipt of the Maiorano complaint on September 10. Its September 21–22 replies to the separate September 20 Bittony referral confirm receipt and review, acknowledge the Director’s separate-report authority, and direct the underlying allegations to MCSO. No certification case number, separate Director report or investigative findings are supplied in those replies.

Maiorano acknowledgment · Bittony referral and LECB replies

October 13 review. The October 27–29 public hearing concerns proposed rules. It is not a disposition of either complaint. Read the notice and participation details.

What would answer it. Identify each matter’s number, reviewer, preservation action and disposition, including whether the Director filed a separate report or LECB contacted MCSO about either matter.