WELL · 42-065-31882 · DISTRICT 10

Barnard-San-Ora #11

Y

Carson County · Panhandle Carson County Field field · Producing  · Vertical

Barnard-San-Ora #11 (API 42-065-31882) is a well in Carson County operated by Cartex Production, completed March 17, 1986 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 23, 1986, permitted to 3,400 ft.

It was permitted by San-Ora Prod. CO. and has since transferred to Cartex Production on the wellbore schedule.

Completion filings report 2 formation tops, including Dolomite, Granite Wash.

Its lease has reported 112K barrels of oil and 334K mcf of gas since January 1993, last reporting in July 2026. The lease carries 12 wells, so these are lease totals, not this well alone.

Operator of record

Cartex Production

Permitted by San-Ora Prod. Co.; the EWA schedule now lists a different operator.

Pampa, TX · P-5 Y, filed Oct 4, 2025 · (805) 459-2916

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCartex Production
Production reportsCartex Productionthrough Mar 2026
Latest permitSan-Ora Prod. Co.Jan 23, 1986

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

3,400
total depth, ft
1
permits on file
Jan 23, 1986
last permit issued
Mar 17, 1986
completed
112K
cumulative oil, bbl
334K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 17, 1986
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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 12 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Barnard-San-Ora O-14-1553Panhandle Carson County FieldCartex Production12112K334KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 1,403 · prior 12 2,431(-42%)

0200400600202420252026

Chain of custody

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

  1. 1San-Ora Prod. Co.Jan 1993 → Sep 2002
  2. 2Cartex ProductionOct 2002 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
296046-99DrillSan-Ora Prod. Co.Jan 23, 1986Jan 23, 1986Jan 28, 19863,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-1553————

Formation tops

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

FormationMD ftSubsea
Dolomite2,555776
Granite Wash2,820511

Perforations

Perforated and open-hole intervals.

FromToType
2,8203,286Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,19112.251,400 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
00Apr 28, 1986Apr 11, 1986Yes
00Apr 25, 1986——

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