WELL · 42-371-38780 · DISTRICT 8

Ponderosa Canyon #10

Y

Pecos County · Toborg field · Shut IN  · Vertical

Ponderosa Canyon #10 (API 42-371-38780) is a well in Pecos County operated by Surge Solutions Inc., completed January 6, 2012 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued December 16, 2010, permitted to 500 ft.

It was permitted by Icanute Energy, Inc. and has since transferred to Surge Solutions Inc. on the wellbore schedule.

Completion filings report one formation top, including Toborg.

Its lease has reported 24.8K barrels of oil since November 2010, last reporting in July 2026. The lease carries 11 wells, so these are lease totals, not this well alone.

Operator of record

Surge Solutions Inc.

Permitted by Icanute Energy, Inc.; the EWA schedule now lists a different operator.

Bandera, TX · P-5 Y, filed Mar 4, 2026 · 8 permits on file · (415) 497-4013

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSurge Solutions Inc.
Production reportsSurge Solutions, Inc.through Mar 2026
Latest permitIcanute Energy, Inc.Dec 16, 2010

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

500
total depth, ft
1
permits on file
Dec 16, 2010
last permit issued
Jan 6, 2012
completed
24.8K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 6, 2012
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 11 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Ponderosa Canyon O-10-41373ToborgSurge Solutions, Inc.1124.8K0Nov 2010 – Jul 2026

Oil, barrels lease total

Last 12 months 898 · prior 12 1,316(-32%)

0200400600202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Merrill Operating, LLCJan 2011 → May 2015
  2. 2White Rock Operating, Inc.Jun 2015 → Jul 2023
  3. 3Surge Solutions, Inc.Sep 2023 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
706925-99DrillIcanute Energy, Inc.Dec 12, 2010Dec 16, 2010Dec 27, 2010500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-41373————

Formation tops

As filed on W-2/G-1. Subsea from 2,415 ft elevation.Download CSV →

FormationMD ftSubsea
Toborg4082,007

Perforations

Perforated and open-hole intervals.

FromToType
408419Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
5.54507.875200 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Dec 18, 2012Jan 26, 2012Yes

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/37138780, documented in the API reference.