WELL · 42-497-34244 · DISTRICT 9

Taylor F #3

Plugged

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

Taylor F #3 (API 42-497-34244) is a plugged well in Wise County, plugged September 30, 2015, last operated by Richey Ray Management CO. Inc..

The RRC has issued one drilling permit, issued April 7, 1998, permitted to 7,000 ft.

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

Completion filings report 3 formation tops, including Parks, Caddo, Bend.

Operator of record

Richey Ray Management Co. Inc.

Permitted by Texas American Resources Company; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Sep 4, 2025 · 136 permits on file · (800) 800-2908

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRichey Ray Management Co. Inc.
Production reportsRichey, Ray Management Co., Inc.through Mar 2013
Latest permitTexas American Resources CompanyApr 7, 1998

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

7,000
total depth, ft
1
permits on file
Apr 7, 1998
last permit issued
Jun 24, 1998
completed
0
cumulative oil, bbl
207K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 1998 THROUGH Sep 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 24, 1998
Shut in
—
Plugged
Sep 30, 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
Taylor "F" G-13-169567Boonsville (Bend Congl., Gas)Richey, Ray Management Co., Inc.10207KJun 1998 – Sep 2015

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. 1Texas American Resources CompanyJun 1998 → Dec 2001
  2. 2Goodrich Petroleum CompanyJan 2002 → Apr 2005
  3. 3Richey, Ray Management Co., Inc.May 2005 → Mar 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
474557-99DrillTexas American Resources CompanyMar 19, 1998Apr 7, 1998Apr 13, 19987,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-169567————

Formation tops

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

FormationMD ftSubsea
Parks4,742-3,766
Caddo5,038-4,062
BendBEND "X"5,650-4,674

Perforations

Perforated and open-hole intervals.

FromToType
5,9445,952Perforated
5,9885,996Perforated
6,2746,280Perforated
6,4666,471Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62575912.25380 S
4.56,5507.875450 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
00Sep 22, 1998Aug 25, 1998Yes
00Sep 3, 1998——

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