WELL · 42-473-31185 · DISTRICT 3

Montgomery #1

Y

Waller County · Brookshire field · NO Production  · Directional

Montgomery #1 (API 42-473-31185) is a well in Waller County operated by Triangle Three Resources L.L.C., completed November 3, 2009 and listed as no production on the RRC schedule.

The RRC has issued one drilling permit, issued December 9, 2008, permitted to 5,000 ft.

Completion filings report 3 formation tops, including Miocene (undifferentiated), Catahoula, Frio.

Its lease has reported 132K barrels of oil and 52.1K mcf of gas since November 2009, last reporting in July 2026. The lease carries 5 wells, so these are lease totals, not this well alone.

Operator of record

Triangle Three Resources L.L.C.

Based in
Dallas, TX
P-5 status
Active (A)
P-5 last filed
Jun 15, 2026
Permits on file
124
Phone
(214) 361-6458

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTriangle Three Resources L.L.C.
Production reportsYordes Energy, LLCthrough Jul 2025
Latest permitTriangle Three Resources L.L.C.Dec 9, 2008

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

5,000
total depth, ft
1
permits on file
Dec 9, 2008
last permit issued
Nov 3, 2009
completed
132K
cumulative oil, bbl
52.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 3, 2009
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.

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 5 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Montgomery O-3-25446BrookshireTriangle Three Resources L.L.C.5132K52.1KNov 2009 – Jul 2026

Oil, barrels lease total

Last 12 months 1 · prior 12 8(-87%)

0100200300202420252026

Chain of custody

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

  1. 1Triangle Three Resources L.L.C.Nov 2009 → Jul 2024
  2. 2Yordes Energy, LLCOct 2024 → Jul 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
675897-99DrillTriangle Three Resources L.L.C.Dec 4, 2008Dec 9, 2008Sep 21, 20095,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-25446————

Formation tops

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

FormationMD ftSubsea
Miocene (undifferentiated)MIOCENE1,200-1,069
Catahoula2,300-2,169
Frio3,000-2,869

Perforations

Perforated and open-hole intervals.

FromToType
4,1204,244Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62564112.25400 S
5.54,2857.8751,020 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
00Feb 24, 2010Nov 12, 2009Yes
00Jan 26, 2010——

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