National Geologic Map Database
Geologic Unit: Arline
Search archives
Map showing publication footprint
  • Usage in publication:
    • Arline formation
  • Modifications:
    • Original reference
  • Dominant lithology:
    • Limestone
  • AAPG geologic province:
    • Appalachian basin

Cooper, G.A., 1956, Chazyan and related brachiopods [U.S.-Canada]: Smithsonian Miscellaneous Collections, v. 127, pt. 1, 1245 p.


Pg. 41-43, chart 1 (facing p. 130). Arline formation. Mostly cobbly weathering impure limestone containing considerable quantities of fine clastic material. Weathers to yellow-brown soil containing numerous silicified fossils. Thickness about 400 feet. Underlies Red Knobs formation (new); overlies Lenoir formation. Thin remnant underlies Effna calcarenites and reefs at Porterfield quarry, Virginia. Includes Fetzer tongue (new), which is recognized in Virginia, Tennessee, and Georgia. Interfingers with silty calcareous beds of Athens formation in southeastern Tennessee and with Rich Valley formation (new) at Marion, Virginia, and vicinity. Fingers of Arline appear in Tellico formation in belt along west front of Great Smoky Mountains. Occurs in area for which Porterfield stage is named. Name attributed to B.N. Cooper and G.A. Cooper. Age is Middle Ordovician (Mohawkian).
Exposed almost in its entirety on both sides of valley of small stream tributary to Gallagher Creek, 2 mi southwest of railroad switch at Arline on Concord (TVA 138-SW) and Louisville (TVA 138-SE) quadrangles, eastern TN.

Source: GNU records (USGS DDS-6; Reston GNULEX).

For more information, please contact Nancy Stamm, Geologic Names Committee Secretary.

Asterisk (*) indicates usage by the U.S. Geological Survey. Other usages by state geological surveys.

"No current usage" (†) implies that a name has been abandoned or has fallen into disuse. Former usage and, if known, replacement name given in parentheses ( ).

Slash (/) indicates name does not conform with nomenclatural guidelines (CSN, 1933; ACSN, 1961, 1970; NACSN, 1983, 2005). This may be explained within brackets ([ ]).