WELL · 42-127-33458 · DISTRICT 1

Briscoe-McKnight #123

Plugged

Dimmit County · Carrizo (San Miguel 2850) field  · Vertical

Briscoe-Mcknight #123 (API 42-127-33458) is a plugged well in Dimmit County, plugged July 24, 2018, last operated by El Toro Resources LLC.

The RRC has issued one drilling permit (amended once), issued May 3, 2007, permitted to 4,000 ft.

It was permitted by Txco Resources Inc. and has since transferred to El Toro Resources LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Escondido, Olmos, San Miguel.

Its lease has reported 1.5K barrels of oil since July 2007, last reporting in September 2018.

Operator of record

EL Toro Resources LLC

Permitted by Txco Resources Inc.; the EWA schedule now lists a different operator.

Oklahoma City, OK · P-5 Y, filed Nov 4, 2025 · 114 permits on file · (432) 238-0069

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEL Toro Resources LLC
Production reportsNewfield Exploration Companythrough Aug 2012
Latest permitTxco Resources Inc.May 3, 2007

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

4,000
total depth, ft
2
permits on file
May 3, 2007
last permit issued
Jun 24, 2007
completed
1.5K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2007 THROUGH Sep 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 24, 2007
Shut in
—
Plugged
Jul 24, 2018

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-McKnight O-1-14837Carrizo (San Miguel 2850)EL Toro Resources LLC11.5K0Jul 2007 – Sep 2018

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. 1Txco Resources Inc.Aug 2007 → Sep 2009
  2. 2Newfield Exploration CompanyMar 2010 → Aug 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
637772-98DrillTxco Resources Inc.Aug 9, 2007May 3, 2007May 3, 20074,000
637772-99DrillExploration Company, TheApr 25, 2007May 3, 2007—4,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-14837————

Formation tops

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

FormationMD ftSubsea
Escondido1,249-551
Olmos2,156-1,458
San Miguel2,970-2,272

Perforations

Perforated and open-hole intervals.

FromToType
2,9903,022Perforated
3,2043,212Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62570912.25325 S
5.53,5247.875485 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
00Aug 22, 2007Aug 13, 2007Yes
00Aug 15, 2007——

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