WELL · 42-041-31960 · DISTRICT 3

Panther Branch Unit No. 1 #1

Plugged

Brazos County · Giddings (Austin Chalk-3) field  · Horizontal

Panther Branch Unit NO. 1 #1 (API 42-041-31960) is a plugged horizontal well in Brazos County, plugged March 27, 2007, last operated by Ogden Resources Ltd..

The RRC has issued one drilling permit (amended once), issued July 11, 2003, permitted to 17,000 ft.

It was permitted by Ogden Resources Corporation and has since transferred to Ogden Resources Ltd. on the wellbore schedule.

Completion filings report one formation top, including Austin Chalk.

Its lease has reported 910 barrels of oil and 10.9K mcf of gas since October 2004, last reporting in May 2007.

Operator of record

Ogden Resources Ltd.

Permitted by Ogden Resources Corporation; the EWA schedule now lists a different operator.

Bryan, TX · P-5 Y, filed Nov 7, 2008 · 7 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOgden Resources Ltd.
Production reportsOgden Resources, Ltd.through Nov 2006
Latest permitOgden Resources CorporationJul 11, 2003

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

17,000
total depth, ft
2
permits on file
Jul 11, 2003
last permit issued
Oct 19, 2004
completed
910
cumulative oil, bbl
10.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2004 THROUGH May 2007

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 19, 2004
Shut in
—
Plugged
Mar 27, 2007

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
Panther Branch Unit No. 1 O-3-24626Giddings (Austin Chalk-3)Ogden Resources, Ltd.191010.9KOct 2004 – May 2007

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. 1Ogden Resources CorporationOct 2004 → Jan 2005
  2. 2Ogden Resources, Ltd.Feb 2005 → Aug 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
533790-98DrillOgden Resources CorporationFeb 17, 2004Jul 11, 2003—15,700
533790-99DrillOgden Resources CorporationJul 2, 2003Jul 11, 2003Aug 24, 200317,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-24626————

Formation tops

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

FormationMD ftSubsea
Austin Chalk11,165-10,937

Perforations

Perforated and open-hole intervals.

FromToType
11,68515,444Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,97512.25537 S
711,6968.75235 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
00Mar 11, 2005Oct 28, 2004Yes
00Nov 29, 2004——

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