WELL · 42-367-00347 · DISTRICT 7

Branson (Light) 320 #1

Plugged

Parker County · Regan (1300) field  · Vertical

Branson (Light) 320 #1 (API 42-367-00347) is a plugged well in Parker County, plugged November 28, 2008, last operated by Mks Natural Gas Company.

The RRC has issued one drilling permit (amended once), issued March 24, 1989, permitted to 4,326 ft.

It was permitted by Cumming Company, Inc. The and has since transferred to Mks Natural Gas Company on the wellbore schedule.

Completion filings report 3 formation tops, including Parks Lime, Pregnant Shale, Bend.

Operator of record

MKS Natural Gas Company

Permitted by Cumming Company, Inc. The; the EWA schedule now lists a different operator.

Weatherford, TX · P-5 Y, filed May 12, 2020 · (817) 682-6651

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMKS Natural Gas Company
Production reportsMKS Natural Gas Companythrough Jan 2008
Latest permitCumming Company, Inc. TheMar 24, 1989

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

4,326
total depth, ft
2
permits on file
Mar 24, 1989
last permit issued
Sep 5, 1989
completed
0
cumulative oil, bbl
13.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 5, 1989
Shut in
—
Plugged
Nov 28, 2008

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
Branson (Light) 320 G-8-131978Regan (1300)MKS Natural Gas Company1013.7KJan 1993 – Nov 2008

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. 1J.E.R. Production Inc.Jan 1993 → Apr 1994
  2. 2Coastal Plains Energy, Inc.Dec 1994 → Oct 2002
  3. 3MKS Consulting CorporationDec 2002 → Jul 2005
  4. 4MKS Natural Gas CompanyAug 2005 → Jan 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
357282-98ReenterCumming Company, Inc. TheSep 18, 1989Mar 24, 1989—4,326
357282-99ReenterCumming Company, Inc. TheMar 22, 1989Mar 24, 1989—4,326

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-131978————

Formation tops

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

FormationMD ftSubsea
Parks Lime1,280-378
Pregnant Shale2,150-1,248
BendBEND CONGLOMERATE4,200-3,298

Perforations

Perforated and open-hole intervals.

FromToType
1,2901,343Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51977.875250 S
8.6251,51512.75—

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
00Oct 10, 1989Sep 15, 1989Yes
00Oct 5, 1989——

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