WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-415-04100

Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof API 42-415-04100Clear

Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.

15 LOG FILES ON 14 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Fuller P.L. #5611__42-415-34232Scurry, TX · Apache Corporation1.07Neutron/Density PorosityTIFFCOMPENSATED Z-DENSILOG COMPENSATED NEUTRON GAMMA RAY100 to 7,652Aug 31, 2006run Jun 24, 2006
Fuller P.L. #5611__42-415-34232Scurry, TX · Apache Corporation1.07ResistivityTIFFDUAL LATEROLOG MICRO LATEROLOG GAMMA RAY1,728 to 7,652Aug 31, 2006run Jun 24, 2006
Fuller P. L. NCT-1 #648142-415-34241Scurry, TX · Crossroads Operating LLC1.18NEUTRON/DENSITY POROSITYTIFF4,790 to 7,461Sep 17, 2009run Sep 25, 2006
P.L. Fuller NCT-1 #60342-415-35237Scurry, TX · Occidental Permian Ltd.1.41ResistivityTIFF4,500 to 7,521Apr 17, 2017
P.L. Fuller NCT-1 #60142-415-35221Scurry, TX · Occidental Permian Ltd.1.64NeutronTIFF0 to 7,450Mar 13, 2017
Cogdell Canyon Reef Unit #643442-415-35227Scurry, TX · Occidental Permian Ltd.1.75NEUTRON POROSITYTIFF0 to 7,200Mar 31, 2017run Dec 22, 2016
Cogdell Canyon Reef Unit #608942-415-03944Scurry, TX · Occidental Permian Ltd.1.78NEUTRON POROSITYTIFF0 to 7,117Dec 8, 2015run Jun 17, 2014
Cogdell Canyon Reef Unit #643542-415-35232Scurry, TX · Occidental Permian Ltd.1.80COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,765 to 7,415Mar 31, 2017run Dec 23, 2016
Fuller B #1__42-415-34966Scurry, TX · Gunn Oil Company1.81RESISTIVITYTIFF1,450 to 5,254May 5, 2015run Feb 6, 2014
Cogdell Canyon Reef Unit #643842-415-35234Scurry, TX · Occidental Permian Ltd.1.90NEUTRON POROSITYTIFF0 to 7,337Mar 31, 2017run Jan 22, 2014
Cogdell Canyon Reef Unit #642842-415-34957Scurry, TX · Occidental Permian Ltd.1.92COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,800 to 7,553Feb 24, 2015run Apr 30, 2014
Cogdell Canyon Reef Unit #6049A42-415-35283Scurry, TX · Occidental Permian Ltd.1.93Gamma RayTIFF4,500 to 7,408Aug 1, 2017
Cogdell Canyon Reef Unit #642942-415-35223Scurry, TX · Occidental Permian Ltd.1.96COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,762 to 7,388May 25, 2017run Dec 1, 2016
Cogdell Canyon Reef Unit #643742-415-35241Scurry, TX · Occidental Permian Ltd.1.96NEUTRON POROSITYTIFF0 to 7,176Mar 31, 2017run Jan 15, 2014
Cogdell Canyon Reef Unit #6023A42-415-35220Scurry, TX · Occidental Permian Ltd.1.99NeutronTIFF4,650 to 7,310Apr 17, 2017

About this data

Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.

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