WELL · 42-157-31853 · DISTRICT 3

Drei Inc. #1

Plugged

Fort Bend County · Pecan Grove SW (8000) field  · Directional

Drei Inc. #1 (API 42-157-31853) is a plugged well in Fort Bend County, plugged September 23, 2015, last operated by Bejo Corporation.

The RRC has issued one drilling permit (amended twice), issued January 7, 1991, permitted to 8,300 ft.

It was permitted by Hallwood Petroleum, Inc. and has since transferred to Bejo Corporation on the wellbore schedule.

Completion filings report 2 formation tops, including 7770' Yegua, 8000' Yegua.

Its lease has reported 114K barrels of oil and 671 mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Bejo Corporation

Permitted by Hallwood Petroleum, Inc.; the EWA schedule now lists a different operator.

Richmond, TX · P-5 Y, filed Dec 6, 2024 · 5 permits on file · (832) 309-0542

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBejo Corporation
Production reportsBejo Corporationthrough Feb 2013
Latest permitHallwood Petroleum, Inc.Jan 7, 1991

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

8,300
total depth, ft
3
permits on file
Jan 7, 1991
last permit issued
Mar 23, 1991
completed
114K
cumulative oil, bbl
671
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 23, 1991
Shut in
—
Plugged
Sep 23, 2015

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
Drei, Inc. O-3-21038Pecan Grove, SW (8000)Bejo Corporation1114K671Jan 1993 – Jul 2026

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. 1Hallwood Petroleum, Inc.Jan 1993 → Jul 1993
  2. 2Bejo CorporationAug 1993 → Feb 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
383116-97DrillHallwood Petroleum, Inc.Jun 18, 1991Jan 7, 1991—8,300
383116-98DrillHallwood Petroleum, Inc.Jan 15, 1991Jan 7, 1991—8,300
383116-99DrillHallwood Petroleum, Inc.Jan 7, 1991Jan 7, 1991Jan 16, 19918,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-21038————

Formation tops

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

FormationMD ftSubsea
7770' Yegua7,788-7,703
8000' Yegua8,650-8,565

Perforations

Perforated and open-hole intervals.

FromToType
8,0718,078Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,38412.25835 S
5.58,2328.5475 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
00Jul 10, 1991Apr 3, 1991Yes
00Jun 25, 1991——

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