Skip to content
Skild Robotics Operations

LGA — Overrides

Scope

LaGuardia Airport (LGA) Terminal B — site-specific overrides and extensions to general SOPs. Site rules take precedence over generic guidance. [SOURCE: SOP V3 §"Site-Specific — LGA Terminal B"]

Operating parameters

ParameterValue
Deployment locationLaGuardia Airport (LGA), Terminal B
Current operating hours9:00 PM – 3:00 AM EST [SOURCE: SOP V3; ABM Ops Manual]
Approved operating areasCCA, CCB, Food Court (Food Court is current active area as of Mar 31, 2026)
Current autonomy stageL0 — Data Collect, Within Arms Reach [SOURCE: SOP V3 + ABM Ops Manual; April 2026 ABM SOP §II]
Robot modelGO2W-26 [SOURCE: ABM Ops Manual]

Operating zones

Three approved operating zones. Only operate in the zone assigned for the shift. [SOURCE: SOP V3 LGA §"Operating Areas"]

  • CCA — Terminal B concourse area A. Boundaries defined by site briefing.
  • CCB — Terminal B concourse area B. Boundaries defined by site briefing.
  • Food Court — current active operating area. Routine runs take place here.

Do not route, teleop, or allow the robot to drift outside the assigned zone. Entering an unapproved area is a reportable incident and can jeopardize the entire deployment. [SOURCE: SOP V3 LGA §"Stay Within the Assigned Zone"]

General SOPs modified by LGA

/robots/go2/setup/pre-flight-checklist/ — extended

Adds the LGA-specific accessories checklist before transport:

  • Spare battery (minimum one, fully charged).
  • Charging brick.
  • Skild tablet + controller.
  • TSA documents (if applicable).
  • Transport case.
  • Body intact, no loose parts, no exposed wires. [SOURCE: SOP V3 LGA §"Accessories Checklist (Hand-Off Inspection)"]

If anything is missing or the robot shows abnormal wear / damage / missing components, stop the hand-off and resolve it before continuing. Do not transport a compromised robot through the terminal.

Adds the on-site shift startup workflow (5 steps). Sequence:

  1. Report on-site and coordinate escort (if required).
  2. Pick up the robot and inspect.
  3. Gate pass and TSA transit (or reverse order if robot is stored inside Terminal B).
  4. Identify and confirm the operating area.
  5. Power on and notify the remote operator. [SOURCE: SOP V3 LGA §"On-Site Shift Startup Workflow"; ABM Ops Manual; April 2026 ABM SOP §III]

/general/communications/ — extended

  • Escort protocol may be required (see below).
  • Power-on Slack message must include: terminal + zone + landmark + any immediate constraints + ready confirmation. [SOURCE: ABM Ops Manual §5]

/general/safety/ — extended

  • Robot must remain powered off and cased during transport through public areas unless otherwise authorized. [SOURCE: SOP V3 §III "Safety Confirmation"; older General Operating Instructions]
  • Robot must not be manually driven on stairs or escalators unless directed by an on-site Skild engineer. [SOURCE: older General Operating Instructions §"Site-specific"; SOP V3 §III]
  • Robot must not be operated in unapproved zones.

/general/incident-response/ — extended

LGA uses a site-specific incident intake form in addition to the universal form. See /sites/lga/incident-response-lga/.

Escort protocol

An escort may be required at LGA for on-site operators from Skild. [SOURCE: SOP V3 LGA §"Escort Protocol"; ABM Ops Manual §1]

If escort is required:

  1. Contact the designated escort via Slack before robot pickup.
  2. Share: your name, role, current location (terminal/level/landmark), planned start time, intended operating area.
  3. Wait at the agreed meeting location. Do not proceed to robot pickup or controlled areas until escort coordination is complete.

Exception: if Kai is the on-site operator, the escort step is not required. Proceed directly to pickup, following all other LGA / ABM requirements. [SOURCE: SOP V3 LGA + ABM Ops Manual §1]

Storage & retrieval

  • Robot is stored in the ABM office (or designated hand-off location) in a secure storage box.
  • At end of shift, robot must be returned to the storage box and locked before the on-site operator departs. [SOURCE: SOP V3 LGA §"Storage and Retrieval"; ABM Ops Manual §"Completion Criteria"]
  • If the robot is kept within Terminal B itself, the gate pass / TSA step happens before pickup, not after.

Do not leave the robot unsecured. The on-site operator does not depart until the robot is physically inside the storage box and the box is locked. Leaving the robot unattended in a public area is a reportable incident. [SOURCE: SOP V3 §XVIII]

Autonomy stage at LGA

Current Stage: L0 — Data Collect, Within Arm’s Reach. On-site operator stays within arm’s reach of the robot at all times. No side conversations. No distractions. Maintained for 5 full shifts after any major software change before progressing. Stages do not progress without explicit Skild / ABM alignment. [SOURCE: SOP V3 §"Autonomy Stages"; ABM Ops Manual §4; April 2026 ABM SOP §II]

Escalation contacts at LGA

  • ABM site coordinator: TBD on work computer (Slack handle not surfaced in available sources).
  • Designated escort: varies by shift; contact via Slack before pickup.
  • Kai — on-site operator who is exempt from the escort step.

Site-specific Slack handles, escort coordinator name, and ABM contact list are not enumerated in available local + Drive sources. Resolve via BACKLOG B-A8.

Conflict / open items at LGA

  • ABM Ops Manual (Mar 31) vs Google Doc (Apr 14) — newer version may have updates not reflected here. See BACKLOG B-A4.
  • 12_SOPs/ subfolder in Track.Go2.ABM.LGA/GO2_LGA_ABM_Intelligence/ not yet enumerated. May contain LGA-specific SOPs already drafted. See BACKLOG B-A5.

Source notes

  • [SOURCE: GO2_Standard_Operating_Procedure_V3.docx] §“Site-Specific — LGA Terminal B” — primary.
  • [SOURCE: ABM Operations Manual.docx] (Mar 31, 2026; maintainers: Anway Shirgaonkar, Robert Belle-Isle, Laura Kasimatis, Jimit Gandhi) — site workflow detail.
  • [SOURCE: GO2_Standard_Operating_Procedure_ABM.docx] (April 2026, Tyler Kugima) — §II Purpose & Scope (LGA Terminal B parameters), §III Start-of-Shift, §VI Hardware Reference (storage location), §XX Incident Reporting. Authoritative for ABM-LGA field operations.
  • [SOURCE: GO2_General_Operating_Instructions_V3.docx] — older companion confirms LGA-specific transport rule.