PERMITS · 748965-97 · DISTRICT 6

Drill: J.P. Beauchamp #A 2H

Expired

Chevron U. S. A. Inc. · Panola County · Horizontal · Final completion

Oct 8, 2012: issued
7,500: permitted depth, ft
42-365-37960: API number
3: versions on file

FIRST SEEN BY PETRORA OCT 8, 2012 · WHY THIS DIFFERS FROM THE ISSUE DATE

Lifecycle

Oct 8, 2012Issued · Permit approved
Jan 8, 2013Received · Application received by the RRC
Jan 14, 2013Amended · Changed after issuance
Mar 8, 2013Spud · Drilling began
Mar 9, 2013Surface casing · Surface string set
Apr 5, 2013Well status · Final completion
Oct 8, 2014Expired · Not drilled within the permit term

A drilling permit is valid for two years from issuance unless extended. How permits work →

Surface location

Acres: 684.14
Nearest town: 1.1 mi SE of Beckville
Nearest lease line: 335 ft

No coordinates yet. The RRC's GIS record usually lands within days of issuance; permits from the historical master file never carry one.

Versions

The RRC numbers versions down from 99: 99 is the original filing, 98 the first amendment. Current version first.

Seq	Type	Operator	Received	Issued	Amended	Depth	Seen
97	Drill	Chevron U. S. A. Inc.	Jan 8, 2013	Oct 8, 2012	Jan 14, 2013	7,500	Oct 8, 2012
98	Drill	Chevron U. S. A. Inc.	Nov 29, 2012	Oct 8, 2012	Dec 12, 2012	7,500	Oct 8, 2012
99	Drill	Chevron U. S. A. Inc.	Sep 27, 2012	Oct 8, 2012	—	7,500	Oct 8, 2012

Application records

Status entries the RRC filed against this permit number.

Status no.	Received	Status	Operator	Lease / well
748965-97	Jan 8, 2013	A	Chevron U. S. A. Inc.	J.P. Beauchamp #A 2H
748965-98	Nov 29, 2012	A	Chevron U. S. A. Inc.	J.P. Beauchamp #A 2H
748965-99	Sep 27, 2012	A	Chevron U. S. A. Inc.	J.P. Beauchamp #A 2H

About this data

W-1 drilling permit from the RRC OGA049M master and daily daf420 files, refreshed every business day. Surface coordinates come from the daily file only. Amendments appear as sequence numbers on the same permit; the lowest is current.

Developers: this page as JSON is GET /v1/data/permits/tx/748965, documented in the API reference.