TEXAS · WELLS · HANSFORD COUNTY · API 42-195-30682 · DISTRICT 08
Collard #1A
Hansford County · Shapley (Morrow) field · Vertical
Collard #1A (API 42-195-30682) is a plugged well in Hansford County, plugged January 19, 1989, last operated by Mewbourne Oil Company.
The RRC has issued one drilling permit, issued April 2, 1979, permitted to 7,500 ft.
Operator of record
- Based in
- Tyler, TX
- P-5 status
- Active (A)RRC P-5 file of Oct 22, 2026
- P-5 last filed
- May 21, 2026
- Permits on file
- 2,064
- Phone
- (903) 561-2900
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Mewbourne Oil Company |
| Production reports | none |
| Latest permit | Mewbourne Oil Co.Apr 2, 1979 |
- 7,500
- total depth, ft
- 1
- permits on file
- Apr 2, 1979
- last permit issued
- Aug 19, 1979
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 19, 1979
- Shut in
- —
- Plugged
- Jan 19, 1989
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.
Wells nearby
Every well with a location on file around this well, in any state, nearest first.
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
Wells named Collard
Mewbourne Oil Company's other wells filed under this lease name in Hansford County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.
Loading the lease's wellsChain of custody
Operator on the lease's P-4
Each operator named on the P-4 filings for this well's lease (a gas well is its own lease), from the date its filing took effect. The P-4 is filed by lease, so a date before the well was drilled is the lease's.
| Operator | From | To |
|---|---|---|
| Mewbourne Oil Company | Aug 19, 1979 | today |
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 46541-99 | Drill | Mewbourne Oil Co. | Apr 2, 1979 | Apr 2, 1979 | Jul 2, 1979 | 7,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Aug 19, 1979 | Collard G-14-84010 | Shapley (Morrow) | Mewbourne Oil Company | Plugged | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,924 | 6,934 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,704 | 12.75 | 1,000 S |
| 2.375 | 6,853 | — | — |
| 4.5 | 7,095 | — | 300 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 12, 1984 | Sep 10, 1979 | — |
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.
- Wellbore filings for 42-195-30682 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-195-30682 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
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/19530682, documented in the API reference.