WELL · 42-157-32167 · DISTRICT 3

Leissner Raymond #1

Plugged

Fort Bend County · Needville North (Yegua EY-2) field  · Vertical

Leissner Raymond #1 (API 42-157-32167) is a plugged well in Fort Bend County, plugged June 16, 2003, last operated by Devon Energy Operating CO. L.P..

The RRC has issued one drilling permit, issued October 9, 2001, permitted to 9,800 ft.

It was permitted by Mitchell Energy Company L.P. and has since transferred to Devon Energy Operating CO. L.P. on the wellbore schedule.

Completion filings report 3 formation tops, including Frio, Vicksburg, Yegua.

Operator of record

Devon Energy Operating Co. L.P.

Permitted by Mitchell Energy Company L.P.; the EWA schedule now lists a different operator.

Oklahoma City, OK · P-5 Y, filed Oct 8, 2004 · 939 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDevon Energy Operating Co. L.P.
Production reportsDevon Energy Operating Co., L.P.through May 2003
Latest permitMitchell Energy Company L.P.Oct 9, 2001

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

9,800
total depth, ft
1
permits on file
Oct 9, 2001
last permit issued
Dec 18, 2001
completed
0
cumulative oil, bbl
369K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2001 THROUGH Jun 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 18, 2001
Shut in
—
Plugged
Jun 16, 2003

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
Leissner, Raymond G-3-187043Needville, North (Yegua EY-2)Devon Energy Operating Co., L.P.10369KDec 2001 – Jun 2003

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. 1Mitchell Energy Company L.P.Dec 2001 → Mar 2002
  2. 2Devon Energy Operating Co., L.P.Apr 2002 → May 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
514317-99DrillMitchell Energy Company L.P.Oct 9, 2001Oct 9, 2001Oct 30, 20019,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-187043————

Formation tops

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

FormationMD ftSubsea
Frio4,465-4,370
Vicksburg6,615-6,520
YeguaTOP YEGUA8,315-8,220
YeguaYEGUA EY-18,745-8,650
YeguaYEGUA EY-28,990-8,895

Perforations

Perforated and open-hole intervals.

FromToType
9,1049,111Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,67513.51,275 S
7.6257,2609.875525 S
4.59,3006.5390 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
00May 6, 2002Feb 20, 2002—
00Mar 13, 2002Jan 17, 2002Yes
00Feb 27, 2002——

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