TEXAS · WELLS · WISE COUNTY · SYLER, J. LEASE · API 42-497-32437 · DISTRICT 7C

Syler J. #1

Plugged

Wise County · Boonsville (Bend Congl. Gas) field  · Vertical

Syler J. #1 (API 42-497-32437) is a plugged well in Wise County, plugged October 12, 2004, last operated by Richey Ray Management CO. Inc..

The RRC has issued one drilling permit, issued July 23, 1982, permitted to 6,900 ft.

It was permitted by Richey & Company, Inc. and has since transferred to Richey Ray Management CO. Inc. on the wellbore schedule.

Its lease has reported 31.9K mcf of gas since January 1993, with no volume in the three years through April 2026.

Operator of record

Richey Ray Management Co. Inc.

Permitted by Richey & Company, Inc.; the EWA schedule now lists a different operator.

Based in
Fort Worth, TX
P-5 status
Active (A)
P-5 last filed
Jan 15, 2026
Permits on file
136
Phone
(817) 246-2455

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRichey Ray Management Co. Inc.
Production reportsRichey, Ray Management Co., Inc.through Feb 2004
Latest permitRichey & Company, Inc.Jul 23, 1982

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

6,900
total depth, ft
1
permits on file
Jul 23, 1982
last permit issued
Oct 19, 1982
completed
0
cumulative oil, bbl
31.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 2004

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 19, 1982
Shut in
—
Plugged
Oct 12, 2004

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
Syler, J. G-13-103021Boonsville (Bend Congl., Gas)Richey, Ray Management Co., Inc.1031.9KJan 1993 – Feb 2004

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. 1Richey, Ray Management Co., Inc.Jan 1993 → Feb 2004

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
167018-99DrillRichey & Company, Inc.Jul 23, 1982Jul 23, 1982Jul 17, 19826,900

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 19, 1982Syler J. G-13-103021Boonsville (Bend Congl. Gas)Richey Ray Management Co. Inc.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
6,1626,168Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62582312.25600 S
2.3756,076——
4.56,2587.875275 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
00Jan 12, 1984Nov 4, 1982—

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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