TEXAS · WELLS · PALO PINTO COUNTY · KIZER LEASE · API 42-363-32945 · DISTRICT 6E

Kizer #1

Plugged

Palo Pinto County · Mineral Wells S.(strawn 3680) field  · Vertical

Kizer #1 (API 42-363-32945) is a plugged well in Palo Pinto County, plugged May 6, 2013, last operated by G & F Oil Inc..

The RRC has issued one drilling permit, issued July 16, 1982, permitted to 5,000 ft.

It was permitted by Raw Energy Corporation and has since transferred to G & F Oil Inc. on the wellbore schedule.

Completion filings report 5 formation tops, including Strawn, Pregnant Shale, Atoka, Big Saline.

Operator of record

G & F Oil Inc.

Permitted by Raw Energy Corporation; the EWA schedule now lists a different operator.

Based in
Aledo, TX
P-5 status
Active (A)
P-5 last filed
Sep 26, 2025
Permits on file
150
Phone
(817) 401-4162

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleG & F Oil Inc.
Production reportsG & F Oil, Inc.through Mar 2001
Latest permitRaw Energy CorporationJul 16, 1982

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

5,000
total depth, ft
1
permits on file
Jul 16, 1982
last permit issued
Jul 14, 1982
completed
0
cumulative oil, bbl
36.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 2013

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 14, 1982
Shut in
—
Plugged
May 6, 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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Kizer G-8-102111Mineral Wells, S.(strawn 3680)G & F Oil, Inc.1036.3KJan 1993 – May 2013

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. 1Jud-Mar EnterprisesJan 1993 → Jul 1993
  2. 2I.T. CorporationOct 1993 → May 1999
  3. 3G & F Oil, Inc.Feb 2001 → Mar 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
166371-99DrillRaw Energy CorporationJul 16, 1982Jul 16, 1982—5,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 14, 1982Kizer G-8-102111Mineral Wells S.(strawn 3680)G & F Oil Inc.Plugged—

Formation tops

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

FormationMD ftSubsea
Strawn2,800-1,849
Pregnant Shale3,260-2,309
AtokaATOKA CONGLOMERATE3,696-2,745
Big SalineBIG SALINE (BEND CONGL)3,969-3,018
Comyn4,498-3,547

Perforations

Perforated and open-hole intervals.

FromToType
3,7043,746Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62535012.25165 S
4.54,5827.875350 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
00Jun 5, 1985Oct 18, 1982—
00Jan 12, 1984——

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