WELL · 42-237-38836 · DISTRICT 9

Montgomery B #1

Y

Jack County · Newark East (Barnett Shale) field · Producing  · Vertical

Montgomery B #1 (API 42-237-38836) is a well in Jack County operated by Century Petroleum Inc., completed April 1, 2005 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 12, 2004, permitted to 7,000 ft.

It was permitted by Eog Resources, Inc. and has since transferred to Century Petroleum Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Marble Falls, Barnett, Estimated Tops.

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

Operator of record

Century Petroleum Inc.

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

Jacksboro, TX · P-5 Y, filed Jan 4, 2026 · 44 permits on file · (940) 507-1400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCentury Petroleum Inc.
Production reportsCentury Petroleum, Inc.through Apr 2026
Latest permitEOG Resources, Inc.Jan 12, 2004

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

7,000
total depth, ft
1
permits on file
Jan 12, 2004
last permit issued
Apr 1, 2005
completed
0
cumulative oil, bbl
127K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 1, 2005
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
Montgomery "B" G-13-209892Newark, East (Barnett Shale)Century Petroleum, Inc.10127KApr 2005 – Jul 2026

Gas, mcf lease total

Last 12 months 6,239 · prior 12 7,091(-12%)

05001K202420252026

Chain of custody

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

  1. 1EOG Resources, Inc.Apr 2005 → Jan 2007
  2. 2Century Petroleum, Inc.Jun 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
556095-99DrillEOG Resources, Inc.Jan 12, 2005Jan 12, 2004Jan 20, 20057,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-209892————

Formation tops

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

FormationMD ftSubsea
Marble Falls5,720-4,644
BarnettBARNETT SHALE5,965-4,889
Estimated Tops——

Perforations

Perforated and open-hole intervals.

FromToType
5,9986,064Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62536612.25220 S
4.56,1007.875710 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
00Jan 27, 2006Nov 15, 2005—
00Oct 12, 2005Jun 16, 2005Yes
00Aug 10, 2005——

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