TEXAS · WELLS · GOLIAD COUNTY · API 42-175-33648 · DISTRICT 02

Moscatelli #1

Plugged

Goliad County · Albrecht (Frio 2450) field  · Vertical

Moscatelli #1 (API 42-175-33648) is a plugged well in Goliad County, plugged October 29, 2007, last operated by Welder Exploration & Prod. Inc..

The RRC has issued 2 drilling permits (amended once) between 2004 and 2006, permitted to 3,500 ft.

Completion filings report 2 formation tops, including Frio, 3250 Zone.

Operator of record

Welder Exploration & Prod. Inc.

Based in
San Antonio, TX
P-5 status
Inactive (I)
P-5 last filed
Mar 9, 2023
Permits on file
346
Phone
(210) 354-1515

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWelder Exploration & Prod. Inc.
Production reportsWelder Exploration & Prod., Inc.through Mar 2007
Latest permitWelder Exploration & Prod., Inc.Apr 18, 2006
3,500
total depth, ft
3
permits on file
Apr 18, 2006
last permit issued
Sep 3, 2005
completed
0
cumulative oil, bbl
167K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2004 THROUGH Oct 2007

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 3, 2005
Shut in
—
Plugged
Oct 29, 2007

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
Moscatelli G-2-220629Albrecht (Frio 2450)Welder Exploration & Prod., Inc.1079.3KSep 2005 – Oct 2007
Moscatelli G-2-207665Goliad, N. (3250)Welder Exploration & Prod., Inc.1087.5KSep 2004 – Feb 2007

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. 1Welder Exploration & Prod., Inc.Sep 2004 → Mar 2007

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
617524-99RecompletionWelder Exploration & Prod., Inc.Apr 12, 2006Apr 18, 2006—3,500
549031-98DrillWelder Exploration & Prod., Inc.Oct 7, 2004Aug 2, 2004—3,500
549031-99DrillWelder Exploration & Prod., Inc.Aug 2, 2004Aug 2, 2004Aug 2, 20043,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Sep 3, 2005Moscatelli G-2-220629Albrecht (Frio 2450)Welder Exploration & Prod. Inc.Plugged—
Sep 21, 2004Moscatelli G-2-207665Goliad N. (3250)Welder Exploration & Prod. Inc.Plugged—

Formation tops

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

FormationMD ftSubsea
Frio2,450-2,274
3250 Zone3,298-3,122

Perforations

Perforated and open-hole intervals.

FromToType
2,4762,482Perforated
3,2983,309Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62543412.25255 S
4.53,4907.875610 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
00Apr 27, 2007May 4, 2006Yes
00Nov 1, 2006——
00Jun 28, 2005Oct 19, 2004Yes
00Apr 19, 2005——

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