TEXAS · WELLS · PECOS COUNTY · BIG CANYON A LEASE · API 42-371-38160 · DISTRICT 7B

Big Canyon A #1211A

Shut in

Pecos County · Pinon (Overthrust) field · Temp Abandoned  · Vertical

Big Canyon A #1211A (API 42-371-38160) is a well in Pecos County operated by Oxy USA Inc., completed January 23, 2009 and listed as temp abandoned on the RRC schedule, shut in January 1, 2009.

The RRC has issued one drilling permit (amended once), issued December 20, 2007, permitted to 16,847 ft.

It was permitted by Sandridge Energy, Inc. and has since transferred to Oxy USA Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Woods Hollow Sand, Caballos.

No lease production has been reported under this well’s leases.

Operator of record

OXY USA Inc.

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

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Jan 26, 2026
Permits on file
3,316
Phone
(713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOXY USA Inc.
Production reportsnone
Latest permitSandridge Energy, Inc.Jan 4, 2008

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

16,847
total depth, ft
2
permits on file
Jan 4, 2008
last permit issued
Jan 23, 2009
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 23, 2009
Shut in
Jan 1, 2009
Plugged
—

Operator's P-5 on the schedule: Active (A)

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Big Canyon A G-10-257539Pinon (Overthrust)OXY USA Inc.100Jan 2009 – Jul 2026

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
651563-98DrillSandridge Energy, Inc.Dec 27, 2007Jan 4, 2008Jan 27, 200820,000
651563-99DrillSandridge Energy, Inc.Dec 17, 2007Dec 20, 2007Jan 27, 200820,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 23, 2009Big Canyon A G-10-257539Pinon (Overthrust)OXY USA Inc.Temp Abandoned · shut in Jan 1, 200916,847

Formation tops

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

FormationMD ftSubsea
Woods Hollow Sand11,483-8,486
Woods Hollow Sand13,120-10,123
Woods Hollow Sand14,413-11,416
Caballos16,603-13,606

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
1696918.51,195 S
10.758,01614.753,405 S
5.516,8316.5445 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 23, 2010Sep 14, 2009Yes
00Sep 30, 2010——

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/37138160, documented in the API reference.