The Pyramid Project Team Update | Matt Beall Podcast

Technological concepts & mission goals

• Project focus (Great Pyramid “air shafts”): Build and deploy robotic systems and ground-penetrating radar (GPR) to investigate structures around and beyond the shaft network that runs from the King’s Chamber and Queen’s Chamber toward the pyramid exterior.

• GPR customization challenge: Off-the-shelf radar isn’t sufficient. The team designs bespoke, lightweight, highly flexible GPR that can be towed by a robot into narrow, hard-to-reach shafts where visibility and navigation are limited.

• Why GPR depth is hard in the pyramid: Radar penetration depends on rock properties. While some limestone environments can work well for GPR, Giza limestone reportedly attenuates radar energy quickly, limiting effective range to roughly 6–8 meters (≈ “about 7 m” discussed).

• Use-case for radar results: The goal is to map reflections (stone-to-air gives strong reflections) to find interfaces and potentially cavities, then guide follow-up investigations with camera/robot access.

Robot + sensing & data processing features

• Robots for shaft ascent: Robotics work targets reliably climbing shafts inclined ~45° (described as ~100% grade) under severe conditions:

  • Dust buildup/glazing on tires reducing traction over distance
  • Block height/side shifts and shaft bends (e.g., left/right angular changes)
  • Navigation complexity increasing toward the top (last ~10 meters hardest)
  • Tether/drag considerations (drag affects pulling or trailing components)

• No-damage constraint: Robots must climb and explore without damaging the shafts.

• Communication/power architecture change: Earlier missions used tethered robots (power/commands from ground). This mission uses fiber-optic communications plus onboard battery power because radars don’t tolerate proximity to metal, affecting system layout.

• High-fidelity mapping suite: Robots collect synchronized multi-sensor data including:

  • Multiple synchronized cameras (six+ high-resolution cameras on angles) for detailed shaft/video survey
  • IMUs for 3D orientation
  • Optical flow to estimate movement/travel based on wall texture
  • Additional distance/measurement sensors (general “suite” described)

• Data analysis pipeline: Massive datasets must be fused for:

  • Localization, reconstruction, mapping, and interpreting what the robot “saw”
  • Converting raw sensor streams into a coherent 3D understanding of shaft geometry and radar-correlated features
  • Multiple algorithm runs/versions (described as ~13–15 versions) to verify results within tight tolerances

Radar interpretation & key technical reasoning

• Radar detection mechanism: Radar “finds” targets via reflections. A true void/cavity (stone-to-air boundary) should produce a strong reflection, but absence of a strong reflection doesn’t guarantee a cavity isn’t there—spaces could be filled with sand/rubble/collapsed material or be less “void-like.”

• Interpreting “big void” claims: The team emphasizes skepticism toward assuming results imply a single “large cavity,” especially without camera ground truth. They stress:

  • Radar is a representation, not a “fish finder” that directly outputs target size/material.
  • Their aim is to identify areas worth further study rather than oversimplified conclusions.

• Comparison to prior work: They reference other methods (notably muon imaging mentioned indirectly) and stress they are doing independent surveys rather than relying on earlier “big void” interpretations.

Results from the Egypt trip (what they did detect)

• Radar performance validated: The team reports that their snake radar worked well enough for their goals and that they likely can refine sensitivity.

• Depth/radius coverage perspective: From the King’s Chamber northern shaft, the effective reach is about 6–8 m, framed as roughly 14–15 feet diameter coverage in all directions around the shaft.

• What was (and wasn’t) seen clearly:

  • Some signals were “surprisingly positive,” others surprisingly negative
  • They did not see the kind of stark signal expected from a “large cavity/empty space” claimed by others
  • Their interpretation suggests possible interfaces but does not confirm a single obvious large cavity at the previously claimed locations

• Next-step logic: “Detect → verify with targeted micro missions”—radar is used as a clue-gathering stage, like a detective collecting evidence, then narrowing to smaller regions.

Transparency, publication, and validation process

• Why not fully public yet: Field results from Egypt must be formally published (per Egyptology rules/permissions). The team avoids broadcasting findings until allowed to preserve permissions and ensure proper peer/official review.

• Ethics of interpretation: They emphasize rigorous interpretation to prevent sensational misinformation (examples included “power plant,” “alien landing site,” etc.), and to avoid the public equating speculative theory with evidence.

• Scientific validation approach:

  • Heavy pre-field simulations and modeling (no perfect “ground truth” in advance, so models are iterated)
  • Pre-calibration using controlled environments where ground truth exists
  • Confidence increases after team consensus that radar interpretation remains consistent (internal verification not necessarily visible to the public)

Planned follow-up (“micro missions” and schedule)

After the major survey, they describe a staged plan:

1. Micro missions (over weeks):

   • Camera insertion via long stick in selected locations, including:
     • Potential cavities near the north/south ends of the Grand Gallery close to the ceiling
     • A crack/hole near the King’s Chamber area (west side mentioned)
   • Ultrasonic/acoustic wall thickness probing (press transducer; estimate thickness/construction)
   • Rover micro-mission(s): endoscope/endoscopy over the door at the end of the Queen’s Chamber north air shaft
   • Possible copper pin recovery if feasible (historic mission goal)
   • Better-resolution video of previously found features (e.g., hieroglyphs from the other shaft)
   • Infrastructure left behind: a permanent pulley to repeatedly deploy “snakes” for future insertions

2. Snake/radar confirmations (next ~8 weeks):

   • Deploy “snakes” more precisely toward targets to confirm/deny radar hypotheses

3. Additional radar firing (next ~8 weeks / later):

   • Attempt radar from relieving chamber access (spaces above King’s Chamber) aimed toward the top of the Grand Gallery

4. Data release goal:

   • Full transparency targeted by January 2027 at the latest, with interim releases and videos expected.

Key “hypothetical outcomes” discussed

• Scenario A (cavity/void found):

  • Shift the plan to the least invasive way to send cameras/robots into the space for direct verification.

• Scenario B (no large void clearly visible):

  • Still not treated as “nothing there.”
  • Focus on weaker hints of spaces/interfaces and continue with more targeted micro missions.

• Reliability question (could scans be wrong?):

  • They argue that while any method can be uncertain, they rely on:
    • extensive pre-calibration and ground-truth validation
    • careful algorithm consensus
    • and they avoid assuming that other methods’ claims or speculation automatically imply a large empty void.

Other forward-looking applications beyond the pyramid

• Broader geophysical + robotics pipeline: The team discusses using radar/LI(D)AR/robotics for other ancient sites, including:
  • Chichén Itzá / Kukulcán area (finding an entrance to a large cenote; potential camera/LiDAR deployment)
  • Inca pyramids in Peru
  • Possible work related to the “Seven Cities of Gold” in the Amazon
  • Mapping an ancient kingdom in Sri Lanka (Rajapur / ~3,000-year-old)

Main speakers/sources (as named in subtitles)

• Matt Beall (podcast host; appears as “Matt Beall / Matt”)
• William Westerway
• Yan Frankie / Ayan (spelled variably) Frankie
• Rob Richardson (subtitle shows “Rob Richom/Rob Richardson”; linked to “University of Leeds” and robotics work)
• Jason Lou (CTO at Acuity Robotics; former University of Leeds; DJedi team)
• Andre Pickering (robotics/robot exploration team member)
• Arjun Nagendran (sensor fusion / data reconstruction / mapping & localization)
• Akahine (lead software specialist; described as chief architect for Mercedes-Benz central computer unit)
• Jake Smith (lead robotics engineer; built the robot for the shaft ascent)

Mentions/related figures:

• Zahi Hawass (permission/publishing authority referenced)
• Dr. He (requested a summary; not further identified by full name in subtitles)