WELL · 42-399-32632 · DISTRICT 7

Pitchford #3

Plugged

Runnels County · Kirkham (Jennings Sand) field  · Vertical

Pitchford #3 (API 42-399-32632) is a plugged well in Runnels County, plugged November 20, 2013, last operated by Sequoia Fossil Fuels Inc..

The RRC has issued 2 drilling permits between 1982 and 1990, permitted to 5,300 ft.

It was permitted by Hilliard Oil and has since transferred to Sequoia Fossil Fuels Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including Palo Pinto, Capps Lm, Jennings Sd, Gardner Lm.

Its 2 leases have reported 4.51K barrels of oil and 15K mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Sequoia Fossil Fuels Inc.

Permitted by Hilliard Oil; the EWA schedule now lists a different operator.

Albany, TX · P-5 Y, filed Jul 4, 2026 · 142 permits on file · (325) 762-3991

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSequoia Fossil Fuels Inc.
Production reportsHilliard Oilthrough Aug 2000
Latest permitHilliard OilNov 7, 1990

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

5,300
total depth, ft
2
permits on file
Nov 7, 1990
last permit issued
Jan 4, 1991
completed
4.51K
cumulative oil, bbl
15K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 4, 1991
Shut in
—
Plugged
Nov 20, 2013

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 2 leases this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Pitchford O-9-12990Kirkham (Jennings Sand)Sequoia Fossil Fuels, Inc.14.51K15KJan 1993 – Jul 2026
— O-9-9911——000—

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. 1Hilliard OilJan 1993 → Aug 2000

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
380186-99ReenterHilliard OilOct 26, 1990Nov 7, 1990Dec 5, 19904,986
179190-99DrillR&H InvestmentsNov 24, 1982Nov 24, 1982Nov 29, 19825,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-9911————
—— O-9-12990————

Formation tops

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

FormationMD ftSubsea
Palo PintoPALO PINTO LM4,135-2,282
Capps LM4,397-2,544
Jennings SD4,812-2,959
Gardner LM4,854-3,001

Perforations

Perforated and open-hole intervals.

FromToType
4,8284,830Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62521211150 S
24,739——
4.54,9867.875150 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 28, 1991Jan 28, 1991—
00Feb 21, 1991——
00Jan 12, 1984Dec 22, 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 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/39932632, documented in the API reference.