WELL · 42-483-32301 · DISTRICT 10

Britt Ranch I 4 #12

Plugged

Wheeler County · Stiles Ranch (Granite Wash Cons) field  · Vertical

Britt Ranch I 4 #12 (API 42-483-32301) is a plugged well in Wheeler County, plugged November 1, 2012, last operated by Le Norman Operating LLC.

The RRC has issued one drilling permit, issued March 14, 2007, permitted to 15,850 ft.

It was permitted by Newfield Expl. Mid-Con. Inc and has since transferred to Le Norman Operating LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Marmaton, Cherokee, Atoka.

Operator of record

LE Norman Operating LLC

Permitted by Newfield Expl. Mid-Con. Inc; the EWA schedule now lists a different operator.

Oklahoma City, OK · P-5 Inactive, filed Oct 31, 2018 · 372 permits on file · (405) 548-1200

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLE Norman Operating LLC
Production reportsNewfield Expl. Mid-Con. Incthrough Aug 2011
Latest permitNewfield Expl. Mid-Con. IncMar 14, 2007

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

15,850
total depth, ft
1
permits on file
Mar 14, 2007
last permit issued
May 13, 2010
completed
0
cumulative oil, bbl
570K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2007 THROUGH Apr 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 13, 2010
Shut in
—
Plugged
Nov 1, 2012

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
Britt Ranch I 4 G-14-239156Stiles Ranch (Granite Wash Cons)LE Norman Operating LLC10570KJun 2007 – Apr 2015

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

Chain of custody

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

  1. 1Newfield Expl. Mid-Con. IncJun 2007 → Aug 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
634854-99DrillNewfield Expl. Mid-Con. IncMar 8, 2007Mar 14, 2007Mar 28, 200715,850

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-239156————

Formation tops

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

FormationMD ftSubsea
Marmaton12,350-9,904
Cherokee13,600-11,154
Atoka14,375-11,929

Perforations

Perforated and open-hole intervals.

FromToType
12,37012,628Perforated
12,68012,818Perforated
13,78414,205Perforated
14,52114,885Perforated
14,97715,292Perforated
15,39215,544Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37544517.5450 S
9.6253,30312.25475 S
5.515,7418.751,200 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 8, 2011Sep 30, 2010—
00Oct 6, 2008Jul 16, 2007Yes
00Sep 25, 2008——

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