TEXAS · WELLS · HOCKLEY COUNTY · MONTGOMERY ESTATE-DAVIES NCT-2 LEASE · API 42-219-36951 · DISTRICT 7B

Montgomery Estate-Davies NCT-2 #182

On schedule

Hockley County · Levelland field · Producing  · Vertical

Montgomery Estate-Davies Nct-2 #182 (API 42-219-36951) is a well in Hockley County operated by Bce-Mach Iii LLC, completed January 18, 2007 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 20, 2006, permitted to 4,820 ft.

It was permitted by Chevron U. S. A. Inc. and has since transferred to Bce-Mach Iii LLC on the wellbore schedule.

Completion filings report one formation top, including San Andres.

Its lease has reported 11M barrels of oil and 3.54M mcf of gas since the record begins in January 1993, last reporting volume in April 2026. The lease carries 198 wells, so these are lease totals, not this well alone.

Operator of record

Bce-Mach III LLC

Permitted by Chevron U. S. A. Inc.; the EWA schedule now lists a different operator.

Based in
Oklahoma City, OK
P-5 status
Active – Extension (X)
P-5 last filed
May 18, 2026
Permits on file
10
Phone
(405) 252-8100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBce-Mach III LLC
Production reportsBce-Mach III LLCthrough Apr 2026
Latest permitChevron U. S. A. Inc.Nov 20, 2006

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

4,820
total depth, ft
1
permits on file
Nov 20, 2006
last permit issued
Jan 18, 2007
completed
11M
cumulative oil, bbl
3.54M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · ON RECORD FROM JAN 1993, THE RECORD'S FIRST MONTH, THROUGH APR 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 18, 2007
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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; they carry 198 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Montgomery Estate-Davies NCT-2 O-11-14567LevellandBce-Mach III LLC19811M3.54Mby Jan 1993 – Apr 2026

Oil, barrels lease total

Last 12 months 170,344 · prior 12 184,895(-8%)

010K20K202420252026

Gas, mcf lease total

Last 12 months 48,895 · prior 12 57,570(-15%)

05K10K202420252026

Wells named Montgomery Estate-Davies NCT-2

Bce-Mach III LLC's other wells filed under this lease name in Hockley County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Texaco E & P Inc.Jan 1993 → May 2002
  2. 2Chevron U. S. A. Inc.Jun 2002 → Sep 2017
  3. 3Sabinal Energy Operating, LLCOct 2017 → Aug 2025
  4. 4Bce-Mach III LLCSep 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
629298-99DrillChevron U. S. A. Inc.Nov 20, 2006Nov 20, 2006Dec 8, 20065,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 18, 2007Montgomery Estate-Davies NCT-2 O-11-14567LevellandBce-Mach III LLCProducing4,820

Formation tops

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

FormationMD ftSubsea
San Andres3,800-195

Perforations

Perforated and open-hole intervals.

FromToType
4,7164,800Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,12612.25935 S
5.54,8207.875980 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Apr 30, 2007Feb 12, 2007Yes
00Feb 20, 2007——

Well logs

1 log loaded from the RRC's log index, the latest received Jun 8, 2007. Neutron. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
Neutron PorosityC.P.N.L.Spans San AndresTIFF3,805 to 4,805Jun 8, 2007run Jan 3, 2007—

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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