WELL · 42-167-31381 · DISTRICT 3

Allar #1

Plugged

Galveston County · Alta Loma SW (12650) field  · Directional

Allar #1 (API 42-167-31381) is a plugged well in Galveston County, plugged July 8, 2015, last operated by Fort Apache Energy Inc..

The RRC has issued one drilling permit (amended 3 times), issued May 8, 2003, permitted to 16,500 ft.

It was permitted by Davis Petroleum Corp. and has since transferred to Fort Apache Energy Inc. on the wellbore schedule.

Operator of record

Fort Apache Energy Inc.

Permitted by Davis Petroleum Corp.; the EWA schedule now lists a different operator.

Based in
Boerne, TX
P-5 status
Active – Extension (X)
P-5 last filed
May 20, 2026
Permits on file
84
Phone
(830) 537-3680

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFort Apache Energy Inc.
Production reportsDavis Petroleum Corp.through Jun 2008
Latest permitDavis Petroleum Corp.May 8, 2003

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

16,500
total depth, ft
4
permits on file
May 8, 2003
last permit issued
Oct 23, 2003
completed
0
cumulative oil, bbl
247K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2003 THROUGH Jul 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 23, 2003
Shut in
—
Plugged
Jul 8, 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Allar G-3-201493Alta Loma, SW (12650)Fort Apache Energy, Inc.10247KOct 2003 – Jul 2015
Allar G-3-201494Alta Loma (Weiting, Lower)Fort Apache Energy, Inc.100Oct 2003 – Jul 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. 1Davis Petroleum Corp.Oct 2003 → Jun 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
531726-96DrillDavis Petroleum Corp.May 19, 2004May 8, 2003Jul 9, 200316,500
531726-97DrillDavis Petroleum Corp.Feb 17, 2004May 8, 2003—16,500
531726-98DrillDavis Petroleum Corp.May 9, 2003May 8, 2003—16,500
531726-99DrillDavis Petroleum Corp.May 8, 2003May 8, 2003—16,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-201493————
—— G-3-201494————

Perforations

Perforated and open-hole intervals.

FromToType
12,55212,564Perforated
12,58612,591Perforated
12,60812,615Perforated
12,63012,638Perforated
12,77212,784Perforated
13,27613,294Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3753,54517.52,800 S
9.6259,88012.251,312 S
5.515,6415.5450 S
515,6416.5450 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
00Aug 12, 2004Apr 28, 2004—
00Jul 20, 2004Mar 17, 2004Yes
00Jun 17, 2004——

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