WELL · 42-127-33473 · DISTRICT 1

Briscoe (5140) #30

Y

Dimmit County · Briscoe Ranch (Olmos) field · Temp Abandoned  · Vertical

Briscoe (5140) #30 (API 42-127-33473) is a well in Dimmit County operated by Flint Oak Energy LLC, completed August 30, 2007 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued July 10, 2007, permitted to 6,000 ft.

It was permitted by Crimson Energy Partners, L.P. and has since transferred to Flint Oak Energy LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Wilcox, Escondido, Olmos.

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

Operator of record

Flint Oak Energy LLC

Permitted by Crimson Energy Partners, L.P.; the EWA schedule now lists a different operator.

Montgomery, TX · P-5 Y, filed Jan 4, 2026 · 14 permits on file · (832) 262-9521

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFlint Oak Energy LLC
Production reportsEnergyquest II, LLCthrough Oct 2012
Latest permitCrimson Energy Partners, L.P.Jul 10, 2007

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

6,000
total depth, ft
1
permits on file
Jul 10, 2007
last permit issued
Aug 30, 2007
completed
0
cumulative oil, bbl
135K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 30, 2007
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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Briscoe (5140) G-1-232719Briscoe Ranch (Olmos)Flint Oak Energy, LLC10135KAug 2007 – Jul 2026

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. 1Crimson Energy Partners, L.P.Aug 2007 → Aug 2008
  2. 2Swift Energy Operating, LLCSep 2008 → Jul 2011
  3. 3Energyquest II, LLCAug 2011 → Oct 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
642037-99DrillCrimson Energy Partners, L.P.Jul 6, 2007Jul 10, 2007Jul 11, 20076,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-232719————

Formation tops

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

FormationMD ftSubsea
Wilcox2,308-1,640
Escondido2,794-2,126
Olmos4,241-3,573

Perforations

Perforated and open-hole intervals.

FromToType
4,4684,486Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62593812.25370 S
4.55,1297.875800 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
00Feb 14, 2008Dec 18, 2007Yes
00Feb 1, 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/12733473, documented in the API reference.